Skip to content
Project management & work tracking

noosh.com

Noosh API application sandbox and mock API

Full description of Noosh API Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
102
Collections
-
Event types
-
Start this simulation
example request
curl https://your-noosh.slurry.io/v1/v1/countries \
  -H "Authorization: Bearer slurry_sim_..."

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

  • GET/1.1/workgroups/{workgroup_id}/projects/{project_id}/fileTags
  • GET/1.1/workgroups/{workgroup_id}/projects/{project_id}/files
  • POST/1.1/workgroups/{workgroup_id}/projects/{project_id}/files
  • GET/1.1/workgroups/{workgroup_id}/projects/{project_id}/files/{file_id}
  • GET/1.1/workgroups/{workgroup_id}/projects/{project_id}/specs/{spec_id}
  • PUT/1.1/workgroups/{workgroup_id}/projects/{project_id}/specs/{spec_id}
  • POST/1.1/workgroups/{workgroup_id}/projects/{project_id}/teammembers
  • GET/1.1/workgroups/{workgroup_id}/specTypes/{spec_type_id}/specTypeFields
  • GET/v1/countries
  • GET/v1/workgroups
  • GET/v1/workgroups/{workgroup_id}/automaticInvitations
  • GET/v1/workgroups/{workgroup_id}/billingRecipients