API documentation

Build on MedGrid.

Two token-authenticated APIs, in opposite directions. Vendors push a catalog in and fulfil the orders that come back out; customers pull their own catalog and pricing and order practice stock from their own system.

An empty developer desk at dusk with code on two monitors

Pick your side of the marketplace

An order with its stage, payment and carrier tracking number

Customer API

Pull your own catalog and pricing, and order practice stock from your own system.

Practices and the systems they run — EHRs, ERPs, ordering portals — and sales channels buying from MedGrid.
Integrations: ShipStation, Shopify and custom connections with sync routing

Vendor API

Sync your catalog, prices and stock, receive signed order webhooks, and report fulfilment.

Vendors integrating their own system — suppliers, distributors, manufacturers and 503A/503B pharmacies.

Both work the same way

A MedGrid administrator issues you a client id and secret — there is no self-service signup for either API. You POST those once to get a bearer token good for one hour, then send it on every call. Responses are wrapped by the framework in a message key.

Cache the token for its full hour. Both token endpoints are rate-limited, and the Customer API counts that limit per source IP rather than per account — an integration that authenticates before every call will lock itself out.

Environments

EnvironmentBase URLUse it for
UAThttps://uat.medgrid.comBuilding and testing your integration.
Productionhttps://medgrid.comReal orders, real money.
They are separate installations with separate databases, so credentials issued on one are unknown to the other. Ask for UAT credentials as well as production ones.

Need a hand?

Our integrations team will pair with you on schema, test data and webhook setup. Reach out through the contact page and choose “Platform Support”.