Skip to content
E-commerce platforms

pims.io

Pims sandbox and mock API

Hereafter is the documentation of the private API of [Pims: Pointages Intelligents pour le Monde du Spectacle](https://pims.io). This API is designed for 3rd-party softwares, editors and partners. Its main purpose is to give access the core data of a Pims customer (i.e. events, ticket counts and promotions). ## Authentication The API uses [basic access authentication](https://en.wikipedia.org/wik Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
28
Collections
-
Event types
-
Start this simulation
example request
curl https://your-pims.slurry.io/api/v1/categories \
  -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 28.

  • GET/categories
  • GET/categories/{category_id}
  • GET/channels
  • GET/channels/{channel_id}
  • GET/events
  • GET/events/{event_id}
  • GET/events/{event_id}/capacities
  • GET/events/{event_id}/capacities/{capacity_id}
  • GET/events/{event_id}/categories
  • GET/events/{event_id}/categories/{category_id}
  • GET/events/{event_id}/channels
  • GET/events/{event_id}/channels/{channel_id}