Skip to content
Energy & utilities

influxdata.com

Influx OSS API Service sandbox and mock API

# Authentication <!-- ReDoc-Inject: <security-definitions> --> Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
197
Collections
-
Event types
-
example request
curl https://your-influxdata.slurry.io/api/v2/ \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 197.

  • GET/
  • GET/authorizations
  • POST/authorizations
  • GET/authorizations/{authID}
  • PATCH/authorizations/{authID}
  • DELETE/authorizations/{authID}
  • GET/buckets
  • POST/buckets
  • GET/buckets/{bucketID}
  • PATCH/buckets/{bucketID}
  • DELETE/buckets/{bucketID}
  • GET/buckets/{bucketID}/labels