Your own website
Use event and schedule data in your own interface. Plan how availability is updated and how visitors proceed to purchase, so outdated dates or offers don’t remain on your website.
Management and integrations / API and automation
Send event and order data to your systems.
If your team needs a website, CRM or internal report of its own, use the API and webhooks. Define what information to transfer, who is responsible for the integration and how the system will be notified of order changes.
Automation for your workflow
Start with a recurring task that has become inconvenient to handle manually.
Internal CRM
Send the order details you need and track status changes. Define record-matching rules so a repeated notification doesn’t create another customer or deal.
Your own analytics
Compile the data you need for an internal report. Clarify what the metrics mean, the date ranges and how refunds are handled before combining platform data with other sources.
Details
What to discuss with your developer in advance
Reading data and changing its state
These involve different levels of access and responsibility. Read access may be enough for a report, while creating or changing events requires separate methods and permissions. Grant access for the specific task.
API and webhooks work together
The API lets you request data or perform an available action. A webhook reports an event, such as an order change. The recipient must interpret the notification and, if needed, check the current state through the API.
Errors and retries are part of the workflow
The network may be unavailable, a notification may be delivered more than once, and data may change before it is processed. Plan for signature verification when using a secret, duplicate prevention and a way to reconcile records after an outage.
From task to tested integration
- 01
Define the data exchange
Choose one specific task: send a paid order to your CRM, update the event list on your website or create an internal report. Specify the required fields, actions and direction of data transfer.
- 02
Check the methods and access
The developer should check the current methods, authorisation scheme and permissions for each operation. Set up secure credential storage and separate error handling.
- 03
Test the complete process
Test order creation, status changes, notification redelivery and what happens when your system is temporarily unavailable. Compare the integration results with the latest data in your account.
Check in advance
Agree on the acceptance criteria
Fields and statuses are defined
It’s clear what data is sent and which event triggers processing.
Access verified
The required methods are available with the selected authentication method, and secrets are stored on the server.
Failures handled
Duplicate notifications and temporary errors won’t result in lost or duplicated data.
FAQs
FAQs
Do I need an API for standard ticket sales?
No. Event pages, sales, orders and check-in are available through the platform interfaces. An API is useful when you want to integrate data or actions into your own software workflows.
What data can I work with?
The organiser API includes operations for events, schedules, ticket categories, registration questions, orders and attendees. Check the current documentation for the specific methods, fields and permissions required for your use case.
What order notifications are available?
Webhooks are available for order.created and order.status_changed. An order being created does not mean it has been paid. The recipient should check the event type and status, and request the order’s current state if needed.
Can a webhook be delivered more than once?
Yes, webhooks may be delivered more than once. Your handler should process repeated notifications safely without creating duplicates in your system. If a secret is configured, a signature is used; the recipient must enable signature verification.
Can one API key be used for every action?
Don’t assume so. The main group of methods supports API keys and user authentication, but some operations specifically require user access. The developer should check each method you need and keep secrets out of your website’s public code.
OBLAKKARTE
Create an accountStart with the process you want to automate
Set up your event and discuss data exchange between Oblakkarte and your system with a developer.