API Reference (coming soon)
The full endpoint reference is on hold while the API settles
The API is still being finalized, so Float isn't publishing an endpoint-by-endpoint reference yet. Endpoints and fields may change before launch. Don't build a production dependency on them.
In the meantime, Get started walks through the core flow with a test key, and the Roadmap says what is real today.
What to expect#
Every request uses an API key that is either test or live. The two environments never share data. See Environments and access.
Creating things is safe to retry. Send an idempotency key and a repeated request returns the original result instead of creating a duplicate.
Two concepts that won't change shape#
Endpoints may move. These two ideas are the foundation of the product and are not expected to.
The business is the subject of everything Float does: underwriting, obligations and reputation all attach to one. Two partners who serve the same business can be linked through a wallet it controls.
Portable, consent-gated, and built only from evidence Float verifies itself. What a partner reports never counts toward it.
Want early access?#
Partner credentials are issued directly for now. See Environments and access.