Skip to content
HRIS & payroll

id4i.de

ID4i sandbox and mock API

ID4i HTTP API Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
107
Collections
-
Event types
-
Start this simulation
example request
curl https://your-id4i-de.slurry.io/api/v1/apikeys \
  -H "Authorization: Bearer slurry_sim_..."

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

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 107.

  • POST/account/password
  • PUT/account/password
  • POST/account/registration
  • PUT/account/registration
  • POST/account/verification
  • GET/api/v1/apikeys
  • POST/api/v1/apikeys
  • GET/api/v1/apikeys/privileges
  • GET/api/v1/apikeys/{key}
  • PUT/api/v1/apikeys/{key}
  • DELETE/api/v1/apikeys/{key}
  • GET/api/v1/apikeys/{key}/privileges