Developers/Fejlesztők

API ReferenceConnect Depoflow to your stack.

The public Depoflow API is not available yet. We're designing the developer layer around the booking, payment, evidence, and event data businesses need to connect Depoflow with their own systems.

Public API

Not available yet.

There are no public API credentials, production endpoints, or published API guarantees at this time. When the API is ready, this page will become the canonical reference for authentication, endpoints, schemas, events, limits, and examples.

Planned API surface

Resources we're designing around.

These represent the product concepts the future API may expose. They are not currently published endpoints or a commitment to a specific final API schema.

Appointments

Appointment records, booking status, and relevant scheduling events.

Planned resource

Payments

Payment authorization records and payment-related events associated with bookings.

Planned resource

Evidence

Structured booking and payment evidence associated with a dispute or protected appointment.

Planned resource

Webhooks

Event delivery for relevant booking and payment activity as the public API evolves.

Planned resource

Integration model

Built around events, not just records.

The future API is intended to make it possible for external systems to work with the important events surrounding a booking, rather than treating Depoflow as another isolated database.

BookingAppointment created or updated

PolicyApplicable terms and acceptance context

PaymentAuthorization and relevant payment events

AppointmentCancellation, no-show, or other lifecycle events

EvidenceStructured record of relevant booking activity

When the API launches

Everything developers need.

Authentication

Endpoint reference

Request & response schemas

Webhook events

Error handling

Rate limits

Idempotency

Integration examples

Building an integration?

Tell us what you need.

If you're planning to connect Depoflow with a booking system, CRM, internal tool, or custom workflow, tell us what you're building and what data or events you need.

Talk to us

Public API documentation will be published when the API is ready