Reference
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.
The generated reference is the source of truth for schemas and responses.
Use the generated reference navigation for supported file types. This guide keeps authentication and registry behavior.
GET /listSupportedDocuments is the one operation on this API that needs no API key. It is a useful first call when you are checking connectivity, because a failure tells you something about the network rather than about your credentials.
GET /document/supported-file-types does require a key, despite sitting in the same group. Do not assume the group is uniformly public.
For the categorised registry as a readable list, see Document Types.
GET /document/supported-file-types
Requires the X-Api-Key header. See Authentication.
Responses
200
OK
SupportedFileTypesResponse
400
Bad Request
ValidationError
401
Authentication required — the X-Api-Key header is missing or invalid.
Example
GET /listSupportedDocuments
No authentication required.
Responses
200
OK
ListSupportedDocumentsResponse
400
Bad Request
ValidationError
Example
Document Types — the same registry, categorised and annotated.
Discovering document types — reading the registry at build time instead of hardcoding it.
Authentication — why one endpoint here is public and the other is not.
Last updated
curl -X GET "https://api-docai-uat.uptiq.ai/document/supported-file-types" \
-H "X-Api-Key: $DOCAI_API_KEY"curl -X GET "https://api-docai-uat.uptiq.ai/listSupportedDocuments"