Authentication
Tracksales API v1 uses organization-scoped API keys. Create keys in Settings → Developer API inside your Tracksales account.
API key format
Keys use the prefix ts_live_ followed by 40 random characters.
API keys access your organization's live data. Use a separate Tracksales organization if you need an isolated environment for integration testing.
Send the key on every request:
Authorization: Bearer ts_live_xxxxxxxxOr:
X-API-Key: ts_live_xxxxxxxxOrganization context
Do not send organization_id in v1 requests. The organization is inferred from the API key server-side.
Scopes
Each key has scopes such as customers:read, invoices:create, invoices:update, or * for full access. Missing scope returns HTTP 403.
Rate limits
120 requests per minute per API key (HTTP 429 when exceeded).
Base URL
All v1 REST endpoints live on the api subdomain. Prepend the base URL below to each endpoint path shown in the API reference (for example /customers becomes https://api.tracksales.co/v1/customers).
Production example: https://api.tracksales.co/v1
Request format
Combine the base URL with the endpoint path from the docs:
Examples:
- List customers:
GET https://api.tracksales.co/v1/customers - Get product:
GET https://api.tracksales.co/v1/products/{uuid} - Create invoice:
POST https://api.tracksales.co/v1/invoices
Send Accept: application/json on every request. Authenticated endpoints also require your API key (see above).