Skip to content
Project management & work tracking

avaza.com

Avaza API Documentation sandbox and mock API

Welcome to the autogenerated documentation & test tool for Avaza's API. <br/><br/><strong>API Security & Authentication</strong><br/>Authentication options include OAuth2 Implicit and Authorization Code flows, and Personal Access Token. All connections should be encrypted over SSL/TLS <br/><br/>You can set up and manage your api authentication credentials from within your Avaza account. (requires Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
86
Collections
-
Event types
-
Start this simulation
example request
curl https://your-avaza.slurry.io/api/Account \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • POST/ScheduleSeries/AddBooking
  • POST/ScheduleSeries/AddLeave
  • PUT/ScheduleSeries/EditBooking
  • PUT/ScheduleSeries/EditLeave
  • GET/api/Account
  • GET/api/Bill
  • POST/api/Bill
  • GET/api/Bill/{id}
  • GET/api/BillPayment
  • POST/api/BillPayment
  • GET/api/BillPayment/{id}
  • GET/api/Company