LOOKME API documentation for developers

Overview

LOOKME Technology Pvt. Ltd. is an API provider based in Burhanpur, India. We supply HTTPS JSON REST endpoints and signed webhooks across SMS, payments, iGaming, esports, dating, MLM, advertising and AI categories. Your engineering team integrates these APIs into mobile apps, websites, admin panels and SaaS platforms.

Base URLs, API keys and sandbox credentials are issued individually after onboarding — they are not published publicly on this website for security reasons.

Authentication

All production requests require HTTPS and server-side API key authentication. Typical header format:

Authorization: Bearer YOUR_API_KEY

Content-Type: application/json

API keys must be stored on your server only. Never embed keys in mobile apps, browser JavaScript or public repositories. Rotate keys when team members leave or credentials may be compromised.

Request conventions

Unless a specific project defines otherwise, LOOKME REST APIs follow these standards:

• JSON request and response bodies with UTF-8 encoding
• UTC timestamps in ISO 8601 format
• Idempotency keys on write operations to prevent duplicates
• Standard HTTP status codes (200, 201, 400, 401, 429, 500)
• Separate sandbox and production environments

POST /v1/{resource}

Content-Type: application/json

Authorization: Bearer YOUR_API_KEY

Idempotency-Key: unique-client-reference



{

  "reference": "your-order-id",

  "payload": {}

}

SMS & communication APIs

Send OTP verification codes, transactional alerts and permitted marketing messages. Features include template management, delivery reports (DLR), two-way inbound messaging, voice OTP fallback and SMPP connectivity for high-volume routes. See the full SMS API product page for example endpoints.

Payment APIs

Where lawfully available through licensed partners, payment endpoints cover merchant onboarding, pay-in collection, payout instructions, transaction status queries and webhook notifications. LOOKME is an API infrastructure provider — settlement and licensing remain with authorised financial institutions. See Payment API details.

Webhooks & callbacks

Asynchronous events — SMS delivery receipts, payment confirmations, game results, conversion events — are POSTed to your registered HTTPS endpoint. Each payload includes a cryptographic signature for verification.

Your endpoint should return HTTP 200 quickly and process events asynchronously. Failed deliveries are retried with exponential backoff. Always verify signatures before acting on webhook data.

Error handling

Errors return a JSON body with an error code and human-readable message. Implement retry logic for 429 (rate limit) and 5xx responses. Do not retry 400-level client errors without fixing the request payload.

Getting API access

There is no public self-serve key registration. To receive documentation, sandbox credentials and production access:

1. 01

   Submit an enquiry

   Fill the contact form with your company name, product description and required API category.

2. 02

   Scope & compliance review

   We confirm applicable regulations, partner availability and integration requirements for your use case.

3. 03

   Sandbox & go-live

   Receive sandbox API keys, test webhooks, then migrate to production with monitoring and support.