Skip to content
Identity & SSO

n-auth.com

nextAuth sandbox and mock API

API for the nextAuth server Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
55
Collections
-
Event types
-
Start this simulation
example request
curl https://your-n-auth.slurry.io/apikeys/ \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.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 55.

  • GET/apikeys/
  • POST/apikeys/
  • GET/attributes/
  • POST/attributes/
  • PUT/attributes/
  • DELETE/attributes/
  • DELETE/attributes/{attributekey}
  • GET/servers/
  • POST/servers/
  • GET/servers/{serverid}/
  • PUT/servers/{serverid}/
  • GET/servers/{serverid}/accounts/