Upload support file (v2 — support_file_code optional)
POST/v2/support-files/upload
Upload a support file. The payload is the same shape as /v1/support-files/upload with one difference: support_file_code is optional.
When support_file_code is provided, RCM skips classification and processes the file synchronously against the provider's support-document catalog (same behaviour as v1). The endpoint returns 204 No Content.
When support_file_code is omitted, RCM persists the file and forwards it to DVS (Document Validation Service) for asynchronous classification before validation. The endpoint returns 202 Accepted with a document_id you can correlate with the webhooks.
The request is multipart/form-data with two parts: the binary file and a request_data JSON part.
Request
Responses
- 202
- 204
- 400
- 401
- 403
- 404
- 406
- 500
Accepted — unclassified upload (support_file_code omitted): file persisted in the inbox and submitted to DVS for asynchronous classification.
No Content — classified upload (support_file_code provided) processed synchronously, same as v1.
Bad Request
Unauthorized
Forbidden - your credentials are not authorised for this operation
Not Found — support_file_code does not exist or is disabled for the provider (error 055-0300-0020). Only applies to the classified path.
File size exceeds maximum allowed
Internal Server Error