Skip to content
Cloud infrastructure/devops

apicurio.local:registry

Apicurio Registry API [v2] sandbox and mock API

Apicurio Registry is a datastore for standard event schemas and API designs. Apicurio Registry enables developers to manage and share the structure of their data using a REST interface. For example, client applications can dynamically push or pull the latest updates to or from the registry without needing to redeploy. Apicurio Registry also enables developers to create rules that govern how regist Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
64
Collections
-
Event types
-
Start this simulation
example request
curl https://your-apicurio-local-registry.slurry.io/admin/artifactTypes \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/admin/artifactTypes
  • GET/admin/config/properties
  • GET/admin/config/properties/{propertyName}
  • PUT/admin/config/properties/{propertyName}
  • DELETE/admin/config/properties/{propertyName}
  • GET/admin/export
  • POST/admin/import
  • GET/admin/loggers
  • GET/admin/loggers/{logger}
  • PUT/admin/loggers/{logger}
  • DELETE/admin/loggers/{logger}
  • GET/admin/roleMappings