Skip to main content
Part of the v1 REST API design-partner preview — no public host yet. YOUR-FLOKIT-API-HOST is a placeholder your FloKit team fills in when you get access.
Use the batch endpoint to send up to 1,000 events per request. Ideal for historical imports, nightly syncs, or high-volume server-side instrumentation where making one request per event is impractical. Endpoint: POST /v1/batch/events

Send a batch


Response

If some events fail validation, the response still returns 200 OK. Successfully validated events are processed; rejected events appear in the errors array with the event index and reason. Your application should inspect rejected and errors after each batch call.

Rate limits

For higher throughput, contact FloKit — dedicated ingest capacity is available for enterprise workspaces.

Historical import

For initial data backfills exceeding 100,000 events, use FloKit → Data → Import to upload a CSV file. For larger datasets or schema mapping assistance, contact FloKit for a managed bulk upload. When sending a historical backfill via the batch API:
  • Sort events by timestamp within each batch to help FloKit process them in order.
  • Use the Idempotency-Key header on each batch request so retries are safe.
  • Spread large imports across multiple requests rather than waiting for a single large upload to complete.