Connect Shiprocket

1Create a dedicated API user — not your login

picoask only reads from Shiprocket, so give it its own API user rather than your owner login. Shiprocket lets you create up to four API users, and each must use an email different from your account login.

• In the Shiprocket panel, open Settings → API → Configure and click Create an API User.
• Enter a new email (e.g. picoask-api@yourbrand.com) and a strong password — not the email you sign in with.
• Under Modules to Access, enable only the read modules you want analysed — Orders, Shipments, Tracking, NDR, Returns and Billing/Statement.
• Set Buyer's Details Access to Not Allowed unless you specifically want customer contact details in your warehouse — picoask never needs them for shipping analytics.
• Click Create User and copy the password now — Shiprocket shows it only once.

Because the API user is separate, you can revoke picoask's access at any time without touching your own login, and its read-only module set keeps it from ever changing your data.

2Connect in picoask

In your project's Integrations tab, choose Shiprocket → Connect and fill in:

• Shiprocket account email — the API user's email from step 1.
• API user password — the password from step 1.

picoask signs in to Shiprocket the moment the connector starts provisioning, so a wrong email or password is reported immediately rather than showing up later as missing data. The password is stored encrypted and used only by the sync worker, which re-authenticates on its own as Shiprocket's login token expires.

3What gets synced

• Shipments — one row per shipment with its courier, AWB, current status, and the order, dispatch, delivery and RTO dates.
• Couriers — the carriers on your account, so performance can be broken down per courier and service.
• Weights & dimensions — entered and volumetric weight, so weight patterns and disputes are visible.
• Delivery & RTO — delivered vs returned-to-origin, dated by the event, so RTO rate and delivery time are answerable.
• Shipping economics — freight and COD charges and the order value, in your own currency, never silently converted.

The first import pulls up to four years of shipment history; after that picoask checks Shiprocket every few hours for orders that changed, so a shipment that delivers or RTOs days later updates in place. Delivery zone, billed-weight reconciliation and NDR reasons are added by a later enrichment pass.

4Troubleshooting

• Login rejected — the email must be the API user's email (not your owner login), and the password must be the one set when the API user was created. Recreate the API user under Settings → API and reconnect.
• "Access refused" on a module — the API user wasn't granted that read module. Edit the API user in Shiprocket, enable the module, and reconnect — no need to make a new one.
• Sync stopped working suddenly — the API user's password was changed or the user was removed. Reconnect with the current password.
• API user option missing — API access can depend on your Shiprocket plan. Check with Shiprocket support that API users are available on your plan.