Skip to content
Floweet
Pro access

Sandbox and production

fw_test_ keys: same data, pitches written from the template without AI, 1,000 calls a day, then going live with an fw_live_ key.

api.floweet.com/v1 · Contract 1.0.0-beta.1 · Beta

Sections · Sandbox
On this page
  1. What changes with a test key
  2. The organization's own data
  3. Going live

The sandbox opens as soon as your organization's API account does, with no commitment. Same address (https://api.floweet.com), same operations, same responses as production: only the key changes, fw_test_… instead of fw_live_….

What changes with a test key

  • Never AI. POST /v1/simulations/{id}/pitch always writes the pitch from the template: the response carries "generator": "template" and no model is called.
  • Daily quota. 1,000 calls a day per organization, reset at midnight UTC, on top of the per-minute limit. Beyond it: 429 test_quota_exceeded.
  • Separate idempotency. An Idempotency-Key used in test never replays a live response, and vice versa.
  • Easy to spot. Every response carries the Floweet-Environment: test header.

The organization's own data

Going live

  1. Write to us at contact@floweet.com: your integration, its use, its expected volume.
  2. Our team reviews the organization and the use, then opens the API account for production.
  3. You receive an fw_live_… key (shown once). Replace the test key: nothing else changes in your code. Until then, a live key answers 403 live_not_enabled.