§01API and webhooks

Your data stays yours, and moves when you say.

A versioned REST API with an OpenAPI schema, scoped keys, signed webhooks and exports. For the day a partner, a website or your own team needs the data too.

All integrations

By application · 2027 season

§02What flows

In and out, always linked.

→From API and webhooks into Yachtbase

  • Requests to the REST API, authenticated by scoped API keys
  • Documented endpoints described by an OpenAPI schema

←From Yachtbase back out

  • Signed webhook deliveries for the events you subscribe to
  • A delivery log, with retry for failed deliveries
  • Exports in CSV, Excel and JSON, such as fleet, bookings, forms and analytics

§03Why it matters

Three things that change.

01

Scoped keys

Create API keys with only the scopes they need, rotate them, and revoke them in a click.

02

Webhooks with receipts

Deliveries are signed and logged, so you can see what was sent and retry what failed.

03

Exports on request

Take your fleet, bookings, form submissions and analytics out as CSV, Excel or JSON.

§04Connect

Three steps to connect.

  1. Step 1

    Create an API key and choose its scopes.

  2. Step 2

    Read the OpenAPI schema and make your first request.

  3. Step 3

    Add a webhook endpoint and choose the events it should receive.

Available now. Available in every workspace.

§05Works with

Where it shows up.

§06Questions

Asked and answered.

Is the API documented?

Yes. It is versioned and described by an OpenAPI schema.

How do I know a webhook came from Yachtbase?

Deliveries are signed. Each one is also written to a delivery log.

Can I limit what a key can do?

Yes. Keys are scoped, and can be rotated or revoked.

Are there safeguards on webhook destinations?

Yes. Outbound URLs are checked to protect against server-side request forgery.

§07Applications open · 2027 season

Bring the whole business aboard.

Fleet, clients, every channel, every signature and every payment, finally in one place.