API overview

Introduction to the SpringOS REST API, base URL, plans required, and what API keys can and cannot do.

The SpringOS REST API lets you push leads into the CRM, sync customer data, and (on Enterprise) list subscribers, create invite links, and read wholesale usage. All endpoints live under /api/v1 and use JSON.

Base URL

https://springos.co

Plan requirements

Pro, Agency, or Enterprise subscription with active access
API keys created in Settings → Integrations (or Enterprise → Integrations)
Pro: 2 keys, 200 requests/minute per key
Agency: unlimited keys, 750 requests/minute per key
Enterprise: unlimited keys, 2,500 requests/minute per key

What API keys cannot do

API keys are not dashboard login. They cannot change branding, billing, team passwords, widget design, or delete accounts. They only access documented /api/v1 routes.

Authentication & key access levels
Bearer token format, full vs restricted keys, and how to create keys safely.
Customers API
Create, list, search, read, and update customer records — the primary lead ingestion endpoint.
Webhooks
Subscribe to CRM events, verify signatures, and handle retries.

API overview

Base URL

Plan requirements

What API keys cannot do

Related articles