TTauracoDocumentation
FREN
The Tauraco siteapp.tauraco.io
Home › Developer portal › Sandbox environments
Document menu← Home
Developer portal
  1. Quick start
  2. Authentication
  3. REST API reference
  4. Webhooks guide
  5. Exports guide
  6. ERP integration guide
  7. Bank integration guide
  8. Tauraco Collateral documentation
  9. MCP documentation
  10. Code samples
  11. Error handling
  12. Sandbox environments
  13. Versions and changelog
  14. FAQ
  15. Developer support
Developers

Sandbox environments

Coming: the launch. The sandbox is built (status on 2026-11-05: isolated stack written and tested on the integration branch) but has never been launched: it is developed, not deployed. No sandbox address is published and no test identifier is distributed today. Launching it is an operator action, following the platform's operations procedure; this page will be updated when the sandbox is actually reachable. The production surfaces, for their part, are online since 2026-11-05 (see Surfaces and addresses); the sandbox stays entirely separate from them.

What is built

An isolated stack, separate from production (database, storage, message queue and services kept apart), in demo mode:

  • two fictitious companies (Senegal, Côte d'Ivoire) with fictitious customers, invoices, payments and journal entries;
  • a fictitious demo bank, a submitted financing request and a fictitious Collateral security interest;
  • a demo partner application, a demo bank client and a demo MCP client; their secrets are shown only once to the operator when the data is loaded, never published;
  • a demo webhook receiver, which verifies the signature and deduplicates deliveries, to see signed deliveries without exposing your own server; it will not be exposed outside the machine hosting the sandbox;
  • responses in the same formats as production.

The sandbox holds no real personal data and no production identifier: loading the demo data is refused outside this environment (three independent checks). Sandbox webhooks can target a plain-HTTP test server, which production forbids. It does not include the web application: the OAuth consent flow (authorization_code) cannot be demonstrated there; client_credentials tokens can.

Meanwhile

  • The Python and TypeScript code samples read their addresses from environment variables (TAURACO_API_BASE, TAURACO_TOKEN_URL): they will be able to target the sandbox unchanged; the others change in one line.
  • Webhook signature verification can be tested offline: the Python and TypeScript samples expose a pure verification function.
  • For an integration project (software vendor, financial institution), write to [email protected].