Skip to content
File storage & documents

dac-static.atlassian.com

Confluence sandbox and mock API

This document describes Confluence's v2 APIs. This is intended to be an iteration on the existing Confluence Cloud REST API with improvements in both endpoint definitions and performance. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
218
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-confluence.slurry.io/wiki/api/v2/admin-key \
  -H "Authorization: Bearer slurry_sim_..."

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

  • GET/admin-key
  • POST/admin-key
  • DELETE/admin-key
  • GET/attachments
  • GET/attachments/{id}
  • DELETE/attachments/{id}
  • GET/attachments/{id}/labels
  • GET/attachments/{id}/operations
  • GET/attachments/{attachment-id}/properties
  • POST/attachments/{attachment-id}/properties
  • GET/attachments/{attachment-id}/properties/{property-id}
  • PUT/attachments/{attachment-id}/properties/{property-id}
Confluence sandbox and mock API | Slurry