API Conventions

These conventions apply across all TemboPlus API products. Read this page once before integrating.

Request format

All requests must:

• Use Content-Type: application/json

• Send request bodies as valid JSON

• Include all required authentication headers (documented per product)

• Include an x-request-id header with a unique UUID v4

---

Request ID (x-request-id)

Every request must include this header. Generate a new UUID for each request.

x-request-id: 550e8400-e29b-41d4-a716-446655440000

Store the x-request-id on your side. If you need to investigate a failed request with TemboPlus support, this is how we trace it.

---

HTTP Status Codes

Code	Meaning	Description
200	OK	Request accepted
400	BAD REQUEST	Invalid payload or headers
401	UNAUTHORIZED	Invalid API credentials. Verify your x-account-id and x-secret-key (or Bearer token for Merchant Accounts)
404	NOT FOUND	Resource does not exist
500	INTERNAL SERVER ERROR	Temporary issue on TemboPlus servers. Retry with exponential backoff. If it persists, contact support with your x-request-id.