Browse documentation
Guides
Authentication
Drishti uses API keys for REST and websocket access. Create or copy a key from the Drishti platform console. Every key is evaluated for product access, route limits, and optional websocket entitlements.
Get an API key
Open the platform console, sign in, and go to the developer portal. Copy an existing key or create a new key for your application.
REST requests
Prefer the X-API-Key header for server-side requests.
curl "https://developers.manasija.in/v1/account" \
-H "X-API-Key: $DRISHTI_API_KEY"The OpenAPI contract also accepts api_key as a query parameter. Use that only for tooling that cannot set headers.
WebSocket requests
Use the same API key on wss://developers.manasija.in/v1/ws. Browser clients typically pass the key in the query string; server clients can use headers where the runtime supports them.
See How to set up WebSockets for a full walkthrough.
wss://developers.manasija.in/v1/ws?api_key=<key>Key restrictions
- Product scopes can limit which REST APIs a key may call.
- Per-key RPM and daily caps can be lower than the account plan.
- WebSocket product access is controlled separately from REST access.
Error codes
| Status | Meaning |
|---|---|
401 | Missing or invalid API key. |
403 | Product, addon, or tier is not permitted. |
429 | Rate or quota limit exceeded. |
402 | Insufficient credits in the application error envelope. |