Skip to main content
All Tenant API requests use an API key created from the tenant dashboard. Requests must be sent to the exact tenant workspace domain, for example https://{tenant}.sinjapp.org/api/v1. The API key does not replace the tenant domain; the domain identifies the workspace before the key is checked. 
X-Api-Key: {tenant_api_key}
Accept: application/json
Keep tenant API keys on your server. Do not expose them in browser-only code or mobile apps distributed to end users. If the request host is not a known tenant domain, the API returns: 
{
  "message": "Tenant could not be identified for this domain."
}

​
Test Your API Key

Use /me to confirm the key belongs to the expected tenant workspace. 
curl "https://{tenant}.sinjapp.org/api/v1/me" \
  -H "X-Api-Key: {tenant_api_key}" \
  -H "Accept: application/json"

​
Scopes

When creating an API key, choose the smallest set of scopes your integration needs.
ScopeUse
messages.sendSend messages and create sender numbers
messages.readRead message logs
contacts.lookupCheck whether a Sinjapp account can receive messages
usage.readRead usage and limits
*Full tenant API access
Sinjapp Business only shows the full API key when it is created or when the tenant dashboard explicitly allows showing an encrypted key.