Both serve the same v1 contract — the same endpoints, request shapes and response schemas. Build against the sandbox, then change the base URL and the key.
Keys are per environment. A sandbox key returns 401 against production and vice versa. Request each one separately when you ask for access.

​
Working in the sandbox

The sandbox is where you should develop. A listing you create there is not visible to real pharmacies and cannot be bought with real money. Two things to know about it:
  • It is also our internal test environment. Your data sits alongside our QA activity, so you may see records you didn’t create. Filter by your own pharmacy NPIs.
  • It carries no stability guarantee. It can receive changes ahead of production, and it is not covered by an uptime commitment. It is for development, not for a demo you can’t reschedule.

​
Moving to production

Production behaves identically, with real consequences: a marketplace listing is a genuine offer to sell, and a cash offer is a genuine offer to buy.
1

Request a production key

Email info@instockrx.com. Include the pharmacy NPIs you’ll be acting for.
2

Confirm your group

Call GET /api/v1/pharmacies/search against production. The pharmacies returned are the ones you can act for — the list may differ from your sandbox group.
3

Switch the base URL

Nothing else in your integration needs to change.
Build the base URL and the key as configuration, not constants. You will move between these two environments more than once.