API limits and bulk capabilities

Returns page sizes, sync/async bulk caps, queued vs running job quotas, supported scopes/operations, and file-ingress capabilities. Agents should configure chunking from this document rather than hard-coding limits.

GET/v1/meta/limits

Authorization

bearerAuth

AuthorizationBearer <token>

Use an account API key in the Authorization header: Authorization: Bearer f_....

In: header

curl -X GET "https://example.com/v1/meta/limits"

{  "data": {    "default_page_size": 20,    "max_page_size": 100,    "bulk_sync_limit": 100,    "bulk_async_limit": 1000,    "max_async_jobs_per_account": 3,    "max_queued_async_jobs_per_account": 25,    "staged_import_append_limit": 500,    "supported_scope_kinds": [      "selection"    ],    "supported_job_operations": [      "api_lead_import"    ],    "file_ingress": {      "staged_json_batches": true,      "presigned_object_upload": true,      "local_path_not_supported": true    }  }}

{  "error": {    "type": "authentication_error",    "code": "invalid_api_key",    "message": "A valid Furnace API key is required"  }}

{  "error": {    "type": "rate_limit_error",    "code": "rate_limit_exceeded",    "message": "Rate limit exceeded for this account"  }}

{  "error": {    "type": "api_error",    "code": "internal_error",    "message": "Internal server error"  }}