IMPACT IN PROGRESS

Technology · API Reference

How we build our APIs.

The conventions we follow across every product's API. We keep endpoint-level detail and request/response specifics for partners directly, rather than publishing them here.

Conventions

What's consistent across our APIs.

These are the principles our APIs follow today, and the ones we'll carry into future products rather than reinventing per product.

Authentication

Every API is accessed with a bearer token tied to your account — no shared secrets, no API keys in query strings.

REST & JSON

Plain REST endpoints over HTTPS, JSON in and JSON out. No proprietary protocol required to get started.

Webhooks

State changes (like a payment settling) are pushed to a URL you configure, rather than requiring you to poll continuously.

Versioning

Endpoints are versioned so we can evolve the API without breaking existing integrations.

Want the specifics?

Talk to us directly.

Endpoint lists, request/response shapes, and authentication details are shared with partners during integration — not published publicly. Reach out and we'll walk you through it.

Get in touch →

Questions about this?

Talk to the team building it.