Find all events for one series in Pims
A documented Pims operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Find all events for one series
- GETReads data · Events
demo.pims.io/series/{series_id}/events
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Pims operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Pims operations
- Get one event channel by IDGET · reads data
- Find all channels for one eventGET · reads data
- Find all ticket counts for one eventGET · reads data
- Get one event by IDGET · reads data
- Find all detailed ticket counts for one eventGET · reads data
- Get one channel by IDGET · reads data
- Find all eventsGET · reads data
- Find all channelsGET · reads data
Questions
- Can HumDay find all events for one series in Pims?
- Yes. This operation is published in Pims's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Pims account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Pims.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Pims account.
Where this came from
Read from a published API description for Pims at cdn.pims.io/api/swagger.json. The description above is the provider’s own wording, not ours. Last published 2018-08-24.