REST API
Create requests, read statuses, manage submissions. Standard HTTP over HTTPS, JSON everywhere.
For developers
Document collection infrastructure for developers
Skip building the upload portal. Connect the request, review and approval workflow over a REST API and webhooks — and ship the parts that make your product yours.
The problem
Rebuilding document collection is expensive and undifferentiated
It always lands on the backlog. Someone has to build all of this — then maintain it forever. None of it is your core product.
Upload UIRequest managementStatus trackingReminder systemReview workflowApproval logic…then maintain it
Use cases
ClientLoop as your document collection layer
A complete, branded document request experience — without you building it. Create requests over REST. React to submissions over webhooks.
- 01Embed in a SaaS product
Fire a document request from inside your app the moment a user hits an onboarding milestone.
- 02Internal dashboard integration
Sync request statuses to your admin panel. Your team sees collection progress without leaving your tool.
- 03Automated onboarding
New account created? Auto-spin a workspace and send the right doc pack. Zero human touch.
- 04Status synchronisation
Webhooks keep your database in lockstep — react in real time to submissions, approvals and change requests.
- 05Client portal replacement
Skip building an upload portal. Use ours, branded, wired to your backend. You get the events; we handle the UX.
What you get
The building blocks of a complete collection system
Webhook events
We push the moment a client submits, an admin requests changes, or a submission is approved. No polling.
Secure client portal
The full client-facing experience — branded workspace, uploads, progress, messaging. You get the outcomes.
Reusable request templates
Define a document pack once, trigger it from an API call. The same request every time.
Approval workflow built in
Review, change requests, approvals, rejections — handled inside ClientLoop. You receive the outcome by webhook.
Authentication and permissions
An API key per workspace. Scoped invite links mean clients only ever see their own data, never each other's.
Example: automated reminder sweep
Scheduled job runsYour automation, on a timer
List outstanding requestsGET via REST API
Trigger reminderPOST to send a nudge
reminder.sent eventWebhook fires back
Ops team notifiedPosted to Slack
The shape of it
You get the events. We handle the UX.
- We host the branded upload portal
- Reminders chase until it's all in
- Review, approve, reject — built in
- Every state change fires a webhook
Security
Isolation, from the ground up
Run ClientLoop as infrastructure and your clients' data stays as safe as if you'd built it yourself. Here's the floor.
- All connections over TLS/HTTPS
- Files encrypted at rest
- Workspace isolation — one customer's data is never accessible to another
- API authenticated with API key per workspace
- Scoped invite links for clients
API access and webhooks are part of the Pro plan and above.
FAQ
Common questions
Is there a public API reference?
The ClientLoop REST API and webhooks are live today, available on the Pro plan. We're continuing to expand endpoint coverage — email info@clientloop.digital with your use case and we'll get you an API key plus current reference docs.
What can the API do right now?
The API supports creating and managing document requests, retrieving submission statuses, managing workspaces, and connecting to external systems. Specific endpoint availability may vary — contact us for the current API reference.
Can I white-label ClientLoop for my product?
Pro plan customers can use custom domains and advanced branding, which makes the client-facing portal appear under their own brand. For deeper product embedding, contact us to discuss your use case.
How do webhooks work?
When you configure a webhook endpoint in your ClientLoop workspace, we send an HTTP POST to your URL when document request events occur — submission received, changes requested, approved, completed. Your server responds with a 200 and processes the payload. See our webhooks page for event details.
What language or framework do I need to use?
None in particular. The ClientLoop API is a standard REST API over HTTPS. Any language or framework that can make HTTP requests and handle JSON responses will work — Python, Node.js, Ruby, Go, PHP, or anything else.
Stop rebuilding what already exists.
ClientLoop handles the whole document collection workflow. You connect via API and build the parts that matter.
Related