API versions — v1 and v2 are retired
Updated
Current state#
| Version | Path | Status |
|---|---|---|
| v1 | /v1/documents | Retired — returns 404 |
| v2 | /v2/documents | Retired — returns 404 |
| v3 | /v3/documents | Live, maintenance only — no new integrations |
| v3.1 | /v3.1/documents | Current. Build against this. |
v1 and v2 are retired and return 404, so no migration window applies — any code still calling them is already broken.
Why v3.1 and not v3#
v3.1 is a strict superset of v3. Same endpoints, plus:
models— discover permitted document types without spending creditsprocessandresult— multi-page document support- Accepts JPG and PNG as well as PDF (v3 is PDF-only)
- Structured, stable error codes on every failure path
- Per-page credit accounting
There is no reason to start on v3.
Base URL and the /api trap#
The public base is https://api.docxtract.io/ with no /api prefix:
✓ https://api.docxtract.io/v3.1/documents
✗ https://api.docxtract.io/api/v3.1/documents → 404If every endpoint returns 404, this is almost always the cause.
Legacy hostnames#
docxtract.rpatech.ai is a legacy alias that redirects to api.docxtract.io. Use api.docxtract.io in new code.
Version reported by health#
GET /v3.1/health returns a version field. If it does not match the version in the path you called, contact support@docxtract.io rather than working around it.
Something wrong or missing on this page? Tell us.