Skip to content

Get started

Authentication

Every request requires your partner API key as a Bearer token in the Authorization header. Keys are environment-scoped.

Building with an assistant? Do not paste this page into a chat; give it one of these instead. /llms-full.txt is the whole documentation as one file written for a model: capabilities, the rules that decide whether an integration works, runnable recipes, every endpoint and every error code, in about 6k tokens. /llms.txt is the short map for tools that follow links, and /openapi.json is the OpenAPI 3.1 contract to generate a typed client from, the same contract the API reference is built from.
Key format: Production keys start with ntzs_live_, test keys with ntzs_test_. Generate or rotate your key from the partner dashboard.
Security: Never expose your API key in client-side or mobile code. All nTZS API calls must originate from your backend server.
curl
curl -X POST https://www.ntzs.co.tz/api/v1/users \
  -H "Authorization: Bearer ntzs_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"externalId":"user_1","email":"user@example.com"}'