Automate Pims

What Pims is

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/wiki

API host: demo.pims.io

What HumDay can read from Pims

These are the operations a schedule or a trigger can watch.

• GETGet one event channel by ID/events/{event_id}/channels/{channel_id}
• GETFind all channels for one event/events/{event_id}/channels
• GETFind all ticket counts for one event/events/{event_id}/ticket-counts
• GETGet one event by ID/events/{event_id}
• GETFind all detailed ticket counts for one event/events/{event_id}/ticket-counts/detailed
• GETGet one channel by ID/channels/{channel_id}
• GETFind all events/events
• GETFind all channels/channels
• GETFind all capacities for one event/events/{event_id}/capacities
• GETFind all categories for one event/events/{event_id}/categories
• GETFind all promotions for one event/events/{event_id}/promotions
• GETFind all series/series
• GETFind all venues/venues
• GETFind all categories/categories
• GETFind all promotions/promotions
• GETGet one event category by ID/events/{event_id}/categories/{category_id}
• GETFind all price ranges/price-ranges
• GETGet one ticket count by ID/events/{event_id}/ticket-counts/{ticket_count_id}
• GETFind all events for one venue/venues/{venue_id}/events
• GETFind all events for one series/series/{series_id}/events
• GETGet one detailed ticket count by ID/events/{event_id}/ticket-counts/detailed/{ticket_count_id}
• GETGet one venue by ID/venues/{venue_id}
• GETGet one series by ID/series/{series_id}
• GETGet one category by ID/categories/{category_id}
• GETGet one promotion by ID/promotions/{promotion_id}
• GETGet one price range by ID/price-ranges/{price_range_id}
• GETGet one capacity by ID/events/{event_id}/capacities/{capacity_id}
• GETFind all promotions for one series/series/{series_id}/promotions

How automating Pims works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Pims account.
4. Grant access, then go live. You approve the specific Pims operations it may use — and only those.

Automate Pims with these

• Magento B2B455 operations
• Klaviyo345 operations
• Agco ATS AGCO277 operations
• BeezUP Merchant210 operations
• Rebilly184 operations
• reverb163 operations
• Jumpseller142 operations
• Swagger API2Cart141 operations
• Just Eat UK97 operations
• Billbee75 operations
• Velopayments Velo Payments75 operations
• Apigee Marketcheck71 operations

Categories

• E-commerce

Questions about Pims automation

Can HumDay connect to Pims?

Yes. HumDay reads Pims's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 28 operations are documented.

Do I need to write code to automate Pims?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Pims account.

What can HumDay do in Pims?

0 of the 28 documented operations change something in Pims, and 28 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Pims account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Pims is held behind that approval.

Where this came from

The operations above are read from a published API description for Pims at cdn.pims.io/api/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2018-08-24.