Skip to content
Feny
Sign inRegister
Create your business
Your business grows with you
Create your business in 5 minutesOnline booking, website and clients — in one place
Sign inRegister
Create your businessNeed help?We are always nearby
© 2026 Feny. All rights reserved.

Feny Developer Platform

Build booking workflows without bypassing the booking engine.

Partner API v1 exposes a scoped catalog, availability, booking lifecycle, and signed delivery contract. Every call is rooted in an application credential, not a caller-supplied tenant.

Get startedView API reference

Integration surface

Discover

Read published services, locations, specialists, and bounded free slots with catalog.read and availability.read.

Reserve

Create a guest booking through the same rules, capacity and payment gates as first-party booking.

Manage

Retrieve, cancel, or reschedule only the opaque booking references created by your own application.

Observe

Receive minimal signed lifecycle events for the application-owned bookings you subscribe to.

Non-negotiable boundaries

  • The API key is the tenant root. Requests never provide business_id, owner_id, account_id, price, paid state, or staff assignment.
  • Write requests require idempotency and the current server version where a state transition is involved.
  • Only published data and opaque partner references leave the API. Guest contacts, internal IDs and stored key material remain private.
  • A sandbox is a separate test tenant and database. It is not a flag that changes production records into test data.
  • Keep API credentials, signing secrets and webhook payload handling on a server you control. Do not expose them to a browser, mobile bundle, URL, analytics tool or support ticket.
Overview | Feny Developers