Sandbox and testing

Test integrations safely when the public API has no documented sandbox mode.

The public REST API and Assistant documentation do not currently define a sandbox, test-mode flag, or separate test base URL. Requests made with a normal token affect its real workspace.

Safe test setup

  • Use a dedicated workspace or, when that is not available, a dedicated inbox and test contacts.
  • Prefix subjects and tags with an unmistakable marker such as [integration-test].
  • Never use real customer email addresses in fixtures.
  • Avoid delete operations unless the test explicitly verifies recovery behavior.
  • Clean up through documented operations and preserve failed fixtures for investigation.
  • Mock ThriveDesk in unit tests and reserve live requests for a small integration suite.

The playground uses production

Requests sent from the API reference target https://api.thrivedesk.com/v1. Review write and delete operations carefully before pressing Send.

SDKs

Use and regenerate the TypeScript, Python, PHP, and Go clients generated from the OpenAPI specification.

Support and contact

Gather actionable diagnostics and contact ThriveDesk about a developer integration.

Safe test setup
Related