Environments

Both services live behind a single, shared API gateway on the api.* domain. Path-based routing sends /store/* to the Store API and /creator/* to the Creator API; the base path is stripped before it reaches the service.

Base URLs

Environment	Gateway host
Production	https://api.elasticstage.com
Staging	https://api.staging.elasticstage.com

Combine the host with the service prefix and the operation path:

API	Prefix	Example
Store API	/store	https://api.staging.elasticstage.com/store/v1/releases
Creator API	/creator	https://api.staging.elasticstage.com/creator/api/v1/creators

Note

The reference pages show operation paths relative to the service (e.g. /v1/releases). Prepend the gateway host and the service prefix from the table above to form the full URL.

Authorization server

OAuth 2.1 authorization and token endpoints are served from the auth.* host:

Environment	Authorization server
Production	https://auth.elasticstage.com/api/auth
Staging	https://auth.staging.elasticstage.com/api/auth

See Authentication for the full flow.

Which environment should I use?

Build and test against staging. It mirrors production behaviour with non-production data, so you can place test orders and fire test webhooks freely. Ask your elasticStage contact to provision production credentials when you’re ready to go live.