Agency API
v1
API Documentation
Agency API
Read intake documents, extracted field data, and form submissions for your agency via a simple, authenticated REST API.
Looking for the embed widget? View Finance Builder Dropzone API →
Live
Version 1.0
JSON · HTTPS
Authentication
Every request must include an
Authorization header containing your Agency API key.Authorization
<agency_api_key>
Your Agency API key, generated in Agency Settings. Passed as-is; hashed with SHA-256 server-side.
Generate an Agency API key in Agency Settings → API Keys. The key is shown once on creation — store it securely.
Example Request Header
Shell
curl https://platform.bindrabbit.com/api/v1/intake_documents \ -H "Authorization: <your_agency_api_key>"
Security Note
Never expose your API keys client-side. All requests should originate from your server. Keys are non-recoverable once generated — if lost, delete the key and generate a new one.
Endpoints
Click an endpoint to expand request and response details.
GET
/api/v1/intake_documents
List Intake Documents
›
Returns all intake documents for your agency, ordered newest first. Only documents belonging to your agency are returned.
Headers
| Header | Required | Description |
|---|---|---|
| Authorization | Required | Your Agency API key (no prefix) |
Response
200
JSON array of intake document objects.
JSON
[ { "id": 42, "file_name": "acord_125.pdf", "status": "approved", "source_channel": "email", "received_from": "broker@example.com", "form_template": "ACORD 25", "fields": { "insured_name": { "label": "Insured Name", "value": "ACME Corp", "confidence": 0.97, "corrected": false } }, "form_submission": { "id": 7, "status": "signed", "api_url": "/api/v1/form_submissions/7" }, "created_at": "2026-06-01T10:00:00.000Z", "reviewed_at": null, "delivered_at": null } ]
401
Invalid or missing API key.
cURL Example
Shell
curl https://platform.bindrabbit.com/api/v1/intake_documents \ -H "Authorization: <your_agency_api_key>"
GET
/api/v1/intake_documents/:id
Get Intake Document
›
Form Submissions
Completed forms submitted by your customers. Each submission belongs to a form template and may reference an originating intake document.
GET
/api/v1/form_submissions
List Form Submissions
›
GET
/api/v1/form_submissions/:id
Get Form Submission
›
Error Handling
The API uses standard HTTP status codes. All error responses include a JSON body.
| Status | Meaning | Common Cause |
|---|---|---|
| 200 | OK | Request succeeded. |
| 401 | Unauthorized | Missing or invalid Authorization header. |
| 404 | Not Found | Document not found or belongs to another agency. |
| 500 | Server Error | Unexpected error. Contact support. |
Error Response Shape
JSON
{ "error": "Invalid API key" }