Skip to content
Cloud infrastructure/devops

appcenter.ms

App Center Client sandbox and mock API

Microsoft Visual Studio App Center API Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
351
Collections
-
Event types
-
Start this simulation
example request
curl https://your-appcenter-ms.slurry.io/v0.1/account/test/export \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/v0.1/account/test/export
  • GET/v0.1/account/test/export/accounts
  • GET/v0.1/account/test/export/featureFlags
  • GET/v0.1/administeredOrgs
  • GET/v0.1/api_tokens
  • POST/v0.1/api_tokens
  • DELETE/v0.1/api_tokens/{api_token_id}
  • GET/v0.1/apps
  • POST/v0.1/apps
  • GET/v0.1/apps/{owner_name}/{app_name}
  • PATCH/v0.1/apps/{owner_name}/{app_name}
  • DELETE/v0.1/apps/{owner_name}/{app_name}