Developer API documentation

Authentication

Requests typically use an HTTPS header such as Authorization: Bearer <api_key> or a project-specific key pair. Keys should be stored on the server, rotated when staff change, and never placed in public mobile apps or client-side JavaScript.

Conventions

Unless a project specifies otherwise, LOOKME REST APIs use JSON request and response bodies, UTC timestamps, idempotency keys for write operations, and documented HTTP status codes. Sandbox and production environments are separated.

POST /v1/{resource}
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "reference": "client-defined-id",
  "payload": {}
}

SMS & communication

Messaging APIs commonly cover OTP, transactional notifications, marketing (where permitted), delivery reports and two-way inbound numbers. SMPP may be offered for higher-volume routes through approved partners.

Payment APIs

Payment endpoints — where lawfully available — may include merchant onboarding hooks, pay-in intents, payout instructions, transaction status and webhook acknowledgements. Settlement and licensing remain with authorised institutions and partners.

Callbacks / webhooks

Asynchronous events such as delivery receipts or transaction updates are sent to a client HTTPS endpoint. Signatures should be verified, responses should return quickly, and failed deliveries should be retried with backoff.

Getting access

There is no public self-serve key issuance on this website. Request documentation, sandbox access or a custom API through the contact form.