Data & direct sales

Exports, Data API & Website Booking

Move operational and accounting data into downstream workflows or connect a booking website to documented booking, pricing, availability, checkout, and payment-status endpoints.

Try for free Read the documentation
  • Operational exports
  • Scoped API keys
  • Idempotent booking flow
OkupAI settings dashboard with booking, check-in, invoice, and city guest report exports
Operational exports Illustration of an API connection between a website and cloud service Idempotent booking flow

What it solves

Use the data without turning the dashboard into another silo.

Accounting, reporting, and direct-booking websites need reliable access to selected operational data. OkupAI provides downloadable exports for common workflows and a deliberately scoped API for supported booking use cases.

How it works

Export a report or build a controlled booking connection

Use filters for human-readable exports, or authenticate a system integration and follow the documented website-booking sequence.

  1. 01

    Choose the data scope

    Filter properties, platforms, and dates for booking, check-in, invoice, or city-guest exports, or create an API key with the intended scope.

  2. 02

    Check price and availability

    A booking website can read supported pricing and availability data, including minimum-stay validation, before attempting to create a stay.

  3. 03

    Create and confirm

    Create the website booking with an idempotency key, request Stripe Checkout when configured, and poll the documented payment-status endpoint.

Built into the workflow

Focused tools for reporting and website booking

Downloadable exports

Generate booking and check-in spreadsheets, invoice archives, and monthly city-guest CSVs with the selected filters.

Scoped API resources

Work with documented booking, pricing, availability, website-booking, Stripe Checkout, and payment-status resources.

Safer booking retries

Use pagination for reads and idempotency for booking creation so a retry does not silently create the same website reservation twice.

Inside OkupAI

The API creates the same operational booking

Website-created stays enter the reservation workflow with property, dates, guests, pricing, payment, and invoice context instead of living in a parallel sales database.

OkupAI booking form illustrating the reservation data used by the website-booking flow

Explore related features

View all features
Direct Bookings, Payments & Invoicing
Channel Manager & Reservations
Properties, Owners & Analytics

Your next connected workflow

Connect the data your workflow actually needs.

Start with the export tools, then use the API reference to design a scoped and secure website-booking integration.

Try for free Read the documentation