Skip to main content

​
Technical FAQ

Technical questions about the SalesOS API, integrations, security, and infrastructure.
The SalesOS API uses JWT (JSON Web Tokens) issued by Auth0. You can obtain tokens via:
  • Client Credentials flow for server-to-server integrations
  • Authorization Code flow for applications acting on behalf of a user
All requests must include the token in the Authorization: Bearer <token> header. See the Authentication guide for details.
Rate limits depend on your plan:
  • Starter: 100 requests/minute
  • Professional: 500 requests/minute
  • Enterprise: 2,000 requests/minute
Rate limit information is included in response headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset). When exceeded, the API returns 429 Too Many Requests.
SSO via SAML is available on the Enterprise plan. SalesOS uses Auth0 as the identity provider, which supports SAML, OIDC, and social login connections. Contact our team to configure SSO for your organization.
If your webhook endpoint does not return a 2xx response, SalesOS retries with exponential backoff:
  • 1st retry after 1 minute
  • 2nd retry after 5 minutes
  • 3rd retry after 30 minutes
  • 4th retry after 2 hours
  • 5th retry after 12 hours
After 5 failures, the event is marked as failed. After 10 consecutive failures across any events, the webhook is automatically deactivated.
Yes. Use the POST endpoints for leads and deals in a loop. Respect rate limits by implementing appropriate delays between requests. For very large imports (10,000+ records), contact support for a bulk import solution that bypasses rate limits.
The API exclusively uses JSON. All request bodies must be Content-Type: application/json. Dates use ISO 8601 format (2026-03-15T14:30:00Z). Currency values are plain numbers (not formatted strings).
Yes. SalesOS provides a staging environment for testing integrations without affecting production data. The staging API base URL and credentials are available in your Admin > Integrations > API Keys panel. Staging data is reset periodically.
All error responses include:
  • An HTTP status code indicating the error category
  • An error code string for programmatic handling
  • A human-readable message
  • A details array for validation errors (which fields failed)
  • A request_id for support reference
Include the request_id when contacting support about API issues.
SalesOS Connect runs on our managed n8n infrastructure. However, you can connect your own n8n instance to SalesOS using the REST API and webhook nodes. Set up SalesOS API credentials in your n8n instance and use the HTTP Request node to call SalesOS endpoints.
The maximum request body size is 1MB. File uploads (attachments) are handled through a separate upload endpoint with a 50MB limit per file.