Use the Store API to read and manage a store from an app or a server integration. Each bearer token belongs to one store and grants specific scopes. Start by confirming the connection, then use the resource endpoints your integration needs.
API version and base URL#
The supported API version is 2025-01. Send requests to https://api-store.tringify.com/api/2025-01. Tokens are pinned to an API version; changing a request URL does not change that pin. Authenticated responses include X-Tringify-API-Version when version validation succeeds. See Versioning and deprecation for how versions are supported and retired.
Make your first request#
Get an app or Store Admin token as described in Authentication. The store must have an active or trialing subscription. GET /discover requires no resource scope, so it is a useful first call.
curl "https://api-store.tringify.com/api/2025-01/discover" \
-H "Authorization: Bearer YOUR_STORE_API_TOKEN"A successful response has success: true and a data object with the connected store, its store type, the token type, API version, and scopes. Compare data.store_id with the store you intended to connect. See Token and store details for every response field.
If data.store_type is dev or transfer, you are connected to a development or transfer store. These stores have smaller rate limits and take test payments only; see Development and transfer stores.
Continue with resource requests#
For example, listing tags requires read_products or the corresponding write_products scope. Send Content-Type: application/json when the endpoint accepts a JSON body. Keep long-lived tokens on your server; in an embedded app, use an App Bridge session token for browser requests.
Read Rate limits and Errors before adding retries. Use Reference data for country, currency, language, and address choices. If your integration reacts to changes, continue to Webhook events.