Skip to content
Cloud infrastructure/devops

bitbucket.org

Bitbucket sandbox and mock API

Code against the Bitbucket API to automate simple tasks, embed Bitbucket data into your own site, build mobile or desktop apps, or even add custom UI add-ons into Bitbucket itself using the Connect framework. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
303
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-bitbucket.slurry.io/2.0/addon/linkers \
  -H "Authorization: Bearer slurry_sim_..."

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

  • PUT/addon
  • DELETE/addon
  • GET/addon/linkers
  • GET/addon/linkers/{linker_key}
  • GET/addon/linkers/{linker_key}/values
  • POST/addon/linkers/{linker_key}/values
  • PUT/addon/linkers/{linker_key}/values
  • DELETE/addon/linkers/{linker_key}/values
  • GET/addon/linkers/{linker_key}/values/{value_id}
  • DELETE/addon/linkers/{linker_key}/values/{value_id}
  • GET/hook_events
  • GET/hook_events/{subject_type}