Integrations

Integrations exist so booking reports flow in continuously from your own systems, and invoices are raised automatically from that data—whether the API client sits on the buyer side, the seller side, or both (per your programme’s rules). That removes duplicate data entry and keeps finance aligned with the operational booking record.

API keys and environments

Developers generate API keys with descriptive names, attach them to production or sandbox environments, and scope read versus write permissions according to least privilege.

Keys can be revoked instantly when compromised or after rotations.

Booking reports over the API

Your applications submit single bookings or batches as structured reports. Expereon maps that payload to the right buyer–seller relationship and materialises invoices automatically (draft or ready states depend on configuration). Downstream, buyers review or auto-approve, and sellers may confirm or dispute when your process requires it.

Treat booking submission as the source of truth for invoice volume: webhooks and logs then help your stack stay in sync when invoices are created or updated from the feed.

Webhooks

Configure webhook endpoints so Expereon can push events to your infrastructure (for example invoice state changes or settlement events—exact catalogues follow your API documentation).

Use retries, idempotency, and monitoring on your side; the platform typically offers logs to debug delivery issues.

Logs and sandbox testing

API logs help developers compare requests and responses during integration hardening.

Always exercise flows end-to-end in sandbox before promoting keys to production, including failure cases (invalid payloads, missing sellers, rate limits).