PLATFORM · CAPABILITY

API and webhooks

The EveryonePlans API is a versioned REST interface over the entire platform — the same interface the product’s own screens are built on — with a consistent response envelope, cursor pagination, idempotency keys on writes, signed webhooks, and a sandbox to build against.

Create a free account See everything else

01THE PROBLEM

Why this is worth having

Most platforms in this category treat the API as an export hatch: a subset of the data, added late, and quietly worse than the interface. That is what makes leaving expensive, and it is why "we have an API" is worth almost nothing as a claim until you check what is actually on it.

02HOW IT WORKS

The mechanism

The interface is a client of this API rather than a privileged layer above it, which is what makes parity structural instead of a promise.
One response envelope and a closed set of error codes, so a client is written once rather than per endpoint.
Idempotency keys on writes, so a retry after a dropped connection replays the original result instead of creating a second record.
Signed webhooks with retries and a visible failure state, so what happens in the platform reaches your systems without polling.
It evolves without breaking under you: new capabilities and fields ship additively, and anything that genuinely has to break ships as a new dated version while the one you built against keeps working.

02bWITHOUT SIGNING IN

What it looks like.

SC-api-and-webhooks · TO BE SUPPLIEDSTILL · 16:9

API and webhooks — screenshot

REAL SCREEN CAPTURE, NOT GENERATED. The webhook delivery view: recent deliveries, one failed and retried, with the signature headers visible. Capture at 1600x900 with believable seeded data — real-looking names, dates within the next two weeks, non-round money amounts — and blur anything identifying a real customer.

DROP AT/art/screens/api-and-webhooks.png

03WORKED EXAMPLE

Your front end, our back end

Your existing site posts its contact form to the intake endpoint.
Your app reads and writes contacts, jobs and invoices with a scoped token.
A webhook tells your systems the moment an invoice is paid.
Nothing about your public design changes, and nothing about your data is locked in.

04QUESTIONS

About api and webhooks

Is the whole product available over the API?

Yes — the interface is a client of the same API, so there is no capability reachable through the screen that is unreachable through the wire. That is the structural version of the promise, rather than a policy that could quietly lapse.

How do I get credentials?

Today we issue them — tell us what you are building and we will set up a client and a sandbox. Self-serve registration from a developer dashboard is being built and is not shipped yet.

05READ NEXT

TRY IT

Reading about it only gets you so far.

Create an account and use it. It costs nothing to look, and you will learn more in twenty minutes of clicking than in any amount of this page.

Create a free account Or ask us something first

API and webhooks

The mechanism

The interface is a client of this API rather than a privileged layer above it, which is what makes parity structural instead of a promise.

One response envelope and a closed set of error codes, so a client is written once rather than per endpoint.

Idempotency keys on writes, so a retry after a dropped connection replays the original result instead of creating a second record.

Signed webhooks with retries and a visible failure state, so what happens in the platform reaches your systems without polling.

It evolves without breaking under you: new capabilities and fields ship additively, and anything that genuinely has to break ships as a new dated version while the one you built against keeps working.