Is the Auth0 Authentication & Management API mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of Auth0 Authentication & Management API (routes, status codes, pagination, webhooks), never real records.

← all adapters

auth0-style

simulates Auth0 Authentication & Management API v2

restadapter v0.1.017 routes

use it

# add to stunt.yaml
services:
  auth0:
    adapter: embedded:auth0-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the Auth0 Authentication & Management API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of Auth0 Authentication & Management API. It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real Auth0 Authentication & Management API v2 surface — the data is fake, the behavior is real.

backing stores

usersrolesoauth_codesrefresh_tokens

routes (17)

GET/.well-known/openid-configuration

GET/.well-known/jwks.json

GET/authorize

POST/oauth/token

GET/userinfo

POST/oauth/revoke

POST/dbconnections/signup

GET/api/v2/users

POST/api/v2/users

GET/api/v2/roles

POST/api/v2/roles

GET/api/v2/users/{id}

PATCH/api/v2/users/{id}

DELETE/api/v2/users/{id}

GET/api/v2/users/{id}/roles

POST/api/v2/users/{id}/roles

DELETE/api/v2/users/{id}/roles

want more of the Auth0 Authentication & Management API surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.