API Documentation
The Parse API provides endpoints to process documents and URLs, extracting structured content. All endpoints require authentication via API key and consume credits based on the number of pages processed.
Base URL
All API requests should be made to:
https://api.parsebridge.com/v1Authentication
All requests require an API key in the Authorization header:
Authorization: Bearer YOUR_API_KEYYou can manage your API keys from the API Keys page in your dashboard.
Endpoints
POST /parse/url
Parse content from a URL.
Request Body
{
"url": "https://example.com/document.pdf"
}Headers
Authorization: Bearer YOUR_API_KEYContent-Type: application/json
Requirements
- URL must be valid and accessible
- Only PDF files are supported
- File size limits apply
- Credits are deducted based on page count
Success Response (200)
{
"success": true,
"content": "extracted content...",
"pageCount": 5,
"creditsUsed": 5
}Error Responses
400— Invalid URL or non-PDF file402— Insufficient credits404— Entitlement not found413— File size too large
POST /parse/document
Parse an uploaded document.
Request
Multipart form data with file upload:
Content-Type: multipart/form-data
file: [PDF file]Headers
Authorization: Bearer YOUR_API_KEYContent-Type: multipart/form-data
Requirements
- File must be provided in
filefield - Only PDF files are supported
- File size limits apply
- Credits are deducted based on page count
Success Response (200)
{
"success": true,
"content": "extracted content...",
"pageCount": 3,
"creditsUsed": 3
}Error Responses
400— No file provided or invalid PDF402— Insufficient credits404— Entitlement not found413— File size too large
Credits
- Credits are consumed based on the number of pages in the document
- 1 page = 1 credit
- Credits are deducted before processing begins
- If processing fails, credits are automatically refunded
- Insufficient credits will result in a 402 error