API tools and SDKs
The playground, Postman collection, and SDKs available for working with the Awell Orchestration API.
Tools for exploring and building against the Orchestration API. All of them need an API key — see Authentication.
GraphQL playground
An in-browser tool for writing, validating and testing GraphQL queries against the API.
Start here when learning the API. Because GraphQL is introspective, the playground shows you the schema as you type, which is faster than reading a reference page to find a field name.
Postman collection
A Postman collection covering the API's operations, for testing outside the browser or sharing a request with a colleague.
Set your API key once at collection level rather than per request.
Server-side SDK
A Node.js SDK for calling the API from a backend.
The Orchestration API is machine-to-machine, so all calls belong on a server that can hold an API key safely. Never call it from a browser or a mobile app; a key in client code is a key anyone can read. See Authentication.
UI library
A set of React components for building your own interface on the API, with a Storybook preview.
⛳ Check before building on this. Navi covers the same job, rendering care flow activities in your own product, and is the actively developed path. If you're starting fresh, start with Navi. Confirm with support@awellhealth.com before choosing the UI library.
Example projects
Awell publishes example projects showing the API in use, which are worth reading before designing your own integration loop. See Domain model for the loop they implement.
Next steps
Next: Domain model, then Start a care flow.