Skip to content
Calendar & scheduling

apacta.com

Apacta sandbox and mock API

API for a tool to craftsmen used to register working hours, material usage and quality assurance. # Endpoint The endpoint `https://app.apacta.com/api/v1` should be used to communicate with the API. API access is only allowed with SSL encrypted connection (https). # Authentication URL query authentication with an API key is used, so appending `?api_key={api_key}` to the URL where `{api_key}` is fou Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
290
Collections
-
Event types
-
Start this simulation
example request
curl https://your-apacta.slurry.io/api/v1/activities \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/activities
  • POST/activities
  • DELETE/activities/bulkDelete
  • PUT/activities/{activity_id}
  • DELETE/activities/{activity_id}
  • GET/cities
  • GET/cities/{city_id}
  • GET/clocking_records
  • POST/clocking_records
  • POST/clocking_records/checkout
  • GET/clocking_records/{clocking_record_id}
  • PUT/clocking_records/{clocking_record_id}
Apacta sandbox and mock API | Slurry