Ocular connects to Shiprocket using two credentials — an API user email (created inside Shiprocket) and the API key that Shiprocket emails to that address.Documentation Index
Fetch the complete documentation index at: https://docs.ocular.dev/llms.txt
Use this file to discover all available pages before exploring further.
What you need
A dedicated API-user email (different from your main Shiprocket login) and the API key emailed to it.
What it unlocks
The Fulfilment data model — AWB-level data, courier costs, RTO status, pincode performance, and cost-discrepancy reconciliation.
Step 1 · Create an API user in Shiprocket
Step 2 · Plug the credentials into Ocular
Open the connector form
In Ocular, navigate to Data Management → Connectors → Add connector → Shiprocket.
Fill the fields
Connector Name
Free-form label.
Connector Identifier
Auto-generated.
Start Date
YYYY-MM-DD — how far back Ocular pulls Shiprocket data.
Lookback Days
Default 30. Increase for long RTO windows.
Schedule Frequency
Numeric value + unit (e.g., 4 hours).
Auto Sync
Toggle on to start sync immediately on create.
The API user email from Step 1.
API Key
The key Shiprocket emailed to that user.
Troubleshooting
API user creation fails
API user creation fails
Almost always because the email you entered matches your main Shiprocket login. Use a unique address — e.g.,
ocular-api@your-domain.com.Didn't receive the API key email
Didn't receive the API key email
Check spam and confirm the email address is correct. If the key still doesn’t arrive, regenerate by deleting and recreating the API user in Settings → API Users.
Authentication errors after a key rotation
Authentication errors after a key rotation
If you’ve created a new API user or rotated the key, update both Email and API Key in the connector form and re-test.
For ticket-writing format when filing a connector issue, see Working with the Ocular team → Connector-not-working tickets.
