Skip to content
Cloud infrastructure/devops

swaggerhub.com

SwaggerHub Registry sandbox and mock API

# Overview Use SwaggerHub Registry API to access, manage, and update the following resources in SwaggerHub, bypassing the web interface: * APIs * Domains * Integrations * Projects * Templates SwaggerHub also provides the [User Management API](https://app.swaggerhub.com/apis-docs/swagger-hub/user-management-api/) to get information about organizations and manage organization members. # Base URL Use Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
87
Collections
-
Event types
-
Start this simulation
example request
curl https://your-swaggerhub.slurry.io/apis \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/apis
  • GET/apis/{owner}
  • GET/apis/{owner}/{api}
  • POST/apis/{owner}/{api}
  • DELETE/apis/{owner}/{api}
  • POST/apis/{owner}/{api}/rename
  • GET/apis/{owner}/{api}/settings/default
  • PUT/apis/{owner}/{api}/settings/default
  • GET/apis/{owner}/{api}/{version}
  • DELETE/apis/{owner}/{api}/{version}
  • POST/apis/{owner}/{api}/{version}/clone
  • GET/apis/{owner}/{api}/{version}/comments