Build document collection into your own workflows.
Create requests, read statuses, approve submissions — standard REST over HTTPS. Live on Pro today.
Document collection shouldn't need a human in the middle
Your CRM, billing and notifications already run themselves. Document collection still waits on someone to create the request, chase the client, and mark it done. The API closes that gap.
What you can do with the ClientLoop API
The full lifecycle of a document request — create to approval. Live on the Pro plan.
- Create a client or contactAdd a client record the moment they appear in your CRM.
- Create a document requestFire a structured request from your own system — you set what's needed and who for.
- Use templates / document packsTrigger a whole pack with one call. Define once, reuse every time.
- Retrieve request statusPending, submitted, under review, approved — no polling loops.
- List outstanding requestsEvery open or overdue request, for dashboards and escalation logic.
- Add feedback to a submissionRequest specific changes before approving, from your own system.
- Approve or reject a submissionClose out a request from your tool — automate the calls a human doesn't need.
- Receive webhook eventsReal-time notifications when a workflow changes. No polling.
Generate a key any time from Settings → API — no waiting on email.
Approve or reject a submission without leaving your system
From event in your system to completed collection
One API-driven loop, start to finish.
- 01Your system fires an event
A client is added, a contract signed, a form completed.
- 02Your code calls the ClientLoop API
Create the client and request, passing details and the template to use.
- 03ClientLoop notifies the client
A secure magic link to their branded workspace. No account needed.
- 04The client uploads their documents
Files and forms, from any device, at their own pace.
- 05Your system is notified via webhook
The submission event hits your endpoint. React immediately.
- 06Admin reviews in ClientLoop
Your team approves or requests changes. Tracked and auditable.
- 07ClientLoop fires the outcome webhook
Approved or completed — file metadata included in the payload.
- 08Your system updates
CRM, database, downstream process — whatever your stack needs.
Simple, secure API key authentication
Pass your key as a Bearer token in the Authorization header. Keep it server-side — never expose it client-side.
Authorization: Bearer YOUR_API_KEY
Content-Type: application/jsonEvery write endpoint supports an Idempotency-Key header so retries never create duplicates.
POST /api/v1/requests
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: 8f14e45f-...
Content-Type: application/json
{
"email": "jane@example.com",
"name": "Jane Smith",
"template": "tmpl_onboarding_individual",
"dueInDays": 7
}200 OK
{
"ok": true,
"clientId": "client_9f2a",
"requestsCreated": 3
}One call finds-or-creates the client by email and sends every document in the Template — full field reference is in the OpenAPI spec.
Common questions
- How do I get access to the API?
- API access is included on the Pro plan — no waiting required. Once you're on Pro, generate a key yourself from Settings → API in your ClientLoop dashboard and start making requests immediately.
- Is there an OpenAPI / Swagger spec?
- Yes — a full OpenAPI spec is published and linked directly from your dashboard's API settings page, importable straight into Postman or Insomnia so you can explore every endpoint without writing a client from scratch.
- Can I use the API to retrieve uploaded files?
- Yes — the API returns submission and file metadata, and a dedicated endpoint mints a temporary, signed download URL (expiring in up to 60 minutes) for the actual file. ClientLoop never creates permanent public links to private client documents.
- What events can I receive via webhook?
- Webhook events cover the document workflow lifecycle — request created, submitted, changes requested, approved, completed — plus reminders sent. See our webhooks page for the full event reference.
- Are there rate limits on the API?
- Yes — requests are rate-limited per workspace (currently 100 requests/minute), which is generous enough for real automations while keeping things fair and sandbox-safe to experiment against.
- Do API keys have limited permissions, like read-only?
- Not today — there are no granular per-key scopes. A key is workspace-isolated (it can only ever see its own workspace's data) and acts with full workspace-admin permissions within that workspace. Keep it as secret as an admin password.
Ready to integrate ClientLoop into your system?
Get your API key and the current endpoint docs. We're happy to walk you through it.