Reference
Doc AI Utility
Discover what the platform can accept before you send it anything.
Last updated
Discover what the platform can accept before you send it anything.
Two lookup endpoints answer the questions every integration asks first: which document types can I name, and which file formats will you take. Both are worth calling at build time rather than hardcoding, because the document-type registry grows without a release — new types are added as configuration.
GET /document/supported-file-types
Requires the X-Api-Key header.
Responses
200
OK
SupportedFileTypesResponse
400
Bad Request
ValidationError
401
Authentication required — the X-Api-Key header is missing or invalid.
Example
curl -X GET "https://<api-host>/document/supported-file-types" \
-H "X-Api-Key: $DOCAI_API_KEY"GET /listSupportedDocuments
No authentication required.
Responses
200
OK
ListSupportedDocumentsResponse
400
Bad Request
ValidationError
Example
Document Types — the same registry, categorised and annotated.
Last updated
curl -X GET "https://<api-host>/listSupportedDocuments"
