Skip to content
Identity & SSO

okta.local

Users (Okta API) sandbox and mock API

The [Okta User API](/docs/api/rest/users.html) provides operations to manage users in your organization. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
19
Collections
-
Event types
-
Start this simulation
example request
curl https://your-okta-local.slurry.io/api/v1/users \
  -H "Authorization: Bearer slurry_sim_..."

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

  • GET/api/v1/users
  • POST/api/v1/users
  • GET/api/v1/users/me
  • GET/api/v1/users/{userId}
  • PUT/api/v1/users/{userId}
  • GET/api/v1/users/{userId}/appLinks
  • POST/api/v1/users/{userId}/credentials/change_password
  • POST/api/v1/users/{userId}/credentials/change_recovery_question
  • POST/api/v1/users/{userId}/credentials/forgot_password
  • GET/api/v1/users/{userId}/groups
  • POST/api/v1/users/{userId}/lifecycle/activate
  • POST/api/v1/users/{userId}/lifecycle/deactivate