Skip to main content
The Endstate API is served from a single base URL. You build, test, and run live traffic against the same endpoints — you isolate development from production data using test chips rather than a separate host.

​
Base URL

All requests go to this base URL. There is no flag or header to switch behavior — what differs is whether you work with test chips or encoded hardware chips.

​
Developing without hardware

You can exercise the full verification flow before you have physical chips. Create a test chip (is_test: true) and use the tap simulator to generate a fresh scan credential, then pass it to the verify endpoint. Test chips behave identically to encoded chips in every API call. See Testing without hardware for a step-by-step walkthrough.

​
HTTPS

HTTPS is required. Plain HTTP requests return 426 Upgrade Required.

​
OpenAPI spec

The OpenAPI specification is served at https://api2.endstate.io/openapi.json.

​
Credentials and limits

Your API key and your organization’s network configuration (read-only on GET /v1/settings) are set up by Endstate during onboarding. Confirm any rate limits or configuration with your Endstate contact.

​
Next steps

Quickstart

Make your first API call end to end.

Authentication

Learn how API keys and session tokens work.