API Reference
Everything you can do in the widgets, you can also do through the 36Blocks APIs.
#
API reference
The full reference is the 36Blocks User API documentation. It covers:
| Module | Use it to |
|---|---|
| Companies & Users | Read the signed-in user's profile and companies, switch or create companies, and manage members. |
| API Keys, Roles & Permissions | Manage a company's API keys, custom roles and permission assignments. |
| OAuth 2.0 | Let third-party apps sign users in with their 36Blocks account. |
| OTP | Send, verify and retry one-time passwords. |
| Server-to-Server | Manage your Block's users, companies, roles and permissions from your backend, using an auth key. |
| Subscriptions & Payments | Subscribe companies to plans, record usage and create payment requests. |
Base URL: https://routes.msg91.com/api
#
Credentials
| Credential | Header | Use it for |
|---|---|---|
| Session token | proxy_auth_token |
Calls made as a signed-in user. |
| Auth key | authkey |
Calls made from your backend. Never put an auth key in a browser or mobile app. |
#
Responses and errors
Most endpoints return { "data": ..., "status": "success", "hasError": false, "errors": [] }. Check hasError: some business errors are returned with HTTP 200. Authentication and permission failures usually return 401, and validation errors return 422 with an errors object listing each field. OAuth token and error responses use plain OAuth-style JSON instead.
Was this helpful?