Skip to content
Other

exlibrisgroup.com:tasklists

Ex Libris APIs sandbox and mock API

For more information on how to use these APIs, including how to create an API key required for authentication, see [Alma REST APIs](https://developers.exlibrisgroup.com/alma/apis). Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
10
Collections
-
Event types
-
Start this simulation
example request
curl https://your-exlibrisgroup-tasklists.slurry.io/almaws/v1/task-lists/printouts \
  -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

All 10.

  • GET/almaws/v1/task-lists/printouts
  • POST/almaws/v1/task-lists/printouts
  • GET/almaws/v1/task-lists/printouts/{printout_id}
  • POST/almaws/v1/task-lists/printouts/{printout_id}
  • GET/almaws/v1/task-lists/requested-resources
  • POST/almaws/v1/task-lists/requested-resources
  • GET/almaws/v1/task-lists/rs/lending-requests
  • POST/almaws/v1/task-lists/rs/lending-requests
  • GET/almaws/v1/task-lists/test
  • POST/almaws/v1/task-lists/test