ParseSphere

Rate Limits & Quotas

These limits protect system stability and ensure consistent performance across all users.

File Size Limits

ParseSphere enforces maximum file sizes for different operations:

Document Parsing: Files up to 50 MB

Dataset Uploads: Files up to 100 MB

Warning

Requests exceeding these limits return a 413 status code before any processing occurs.

json
{
"detail": "File too large (55.0MB). Maximum allowed: 50MB"
}

Working with Large Files

For files exceeding size limits, consider compressing the document or splitting it into smaller parts before upload.

Query Execution Limits

Natural language queries have the following constraints:

Maximum Datasets per Query: 10 datasets

Query Execution Timeout: 60 seconds

Result Set Cap: 1,000 rows

Information

Queries that exceed 60 seconds of execution time are terminated and return a timeout error. Result sets are capped at 1,000 rows.

json
{
"detail": "Query execution timeout after 60 seconds",
"sql_queries_executed": [
  {
    "step": 1,
    "sql": "SELECT * FROM large_dataset",
    "success": false,
    "error": "Query exceeded maximum execution time"
  }
]
}

Tip

If you need to work with larger datasets, add specificity to your question or use aggregations instead of requesting all rows.

Result Caching

Parse results remain cached for efficient retrieval:

Default Cache Duration: 24 hours

Configurable Range: 60 seconds to 86,400 seconds (24 hours)

Behavior: Subsequent requests for the same parse_id return cached results without reprocessing.

Configure Cache Duration

Override the default duration with the session_ttl parameter:

bash
curl -X POST https://api.parsesphere.com/v1/parses \
-H "Authorization: Bearer sk_your_api_key" \
-F "file=@document.pdf" \
-F "session_ttl=3600"  # 1 hour

Shorter TTLs reduce storage costs for high-volume integrations

Longer TTLs improve response times for frequently accessed documents

API Versioning

The current API version is v1, specified in the URL path:

bash
# All endpoints use /v1/ in the path
https://api.parsesphere.com/v1/parses
https://api.parsesphere.com/v1/workspaces
https://api.parsesphere.com/v1/api-keys

Version Policy

Information

Version increments (v2, v3) occur only for breaking changes—removed endpoints, changed response structures, or altered parameter semantics.

Breaking changes that trigger new versions:

  • Removed endpoints
  • Changed response structures
  • Altered parameter semantics

Non-breaking changes shipped within existing versions:

  • New optional parameters
  • Additional response fields
  • New endpoints

Warning

Monitor the changelog for deprecation notices before version transitions. We provide advance notice for all breaking changes.

What's Next?

Learn more about API usage: