Door detection processing time (free tier)
This applies only to door detection (POST /v1/drawings/detection/doors).
Free-tier door detection typically completes in 2–4 minutes per job. Processing time scales mainly with page count and drawing complexity — a dense multi-page set takes longer than a single sheet.
Need it faster? Pro and Enterprise plans run detection on dedicated GPU infrastructure.Upgrade your plan →
/v1/drawings/detection/doorsDetect doors in architectural floor-plan PDFs. Accepts a previously uploaded document_id, enqueues inference, and returns a job you poll for results. Detections are returned as bounding boxes in PDF coordinate space.
Request
Auth via X-API-Key header. Body is JSON — the endpoint does not accept file uploads directly; upload your PDF first via POST /v1/documents to get a document_id.
Credits are charged on submission based on len(page_numbers) (or the document's total page count when omitted) — not on pages that actually contain doors. Send only valid page indices to avoid over-billing.
Code examples
Response — 202 Accepted
The job is enqueued immediately. Poll GET /v1/jobs/{job_id} until status is complete or failed.
Result shape
When status === "complete" and model === "door-detector", the result field on the job contains:
The doors list is post-filtered by a geometry and median-area pipeline before being returned. doors_found always reflects the filtered count — raw unfiltered counts are not exposed.
Credits & rate limits
Rate-limit 429s include retry_after_seconds in the body. Quota 429s and rate-limit 429s return the same status code — check the error body to distinguish them.
Errors
Response Preview
{ "job_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7", "status": "queued", "poll_url": "/v1/jobs/7c9e6679-7425-40de-944b-e07fc1f90ae7" }