Submit Partner Subaccount Document

### Upload a document for a subaccount request. **Available to:** Organization administrators **Environments:** Production **Rate Limit:** 10 requests per 30 seconds with time penalty for exceeding the limit After creating a subaccount request, use this endpoint once per `documentType` to upload each of the three required documents. | Document | `documentType` | | ---------------------------- | -------------------------------- | | Power of Attorney (POA) Form | `POAForm` | | Government ID | `Id` | | Proof of Address | `ResidentialAddressConfirmation` | <Warning>**Warning:** This endpoint returns **HTTP 200** for successes **and** business errors. Always check the `errorText` field in the response body to determine whether the request succeeded or failed.</Warning> **subAccountRequestId** For `subAccountRequestId`, use the `requestId` returned from `createpartnersubaccountrequest`. **`base64data` Format** Documents are submitted inline as base64 data URIs. The `base64data` field must be a data URI with a supported MIME type prefix. The maximum field length is 8,388,608 characters (approximately 6 MB). ``` data:<mime-type>;base64,<base64-encoded-content> ``` Supported MIME types: - `application/pdf` - `text/plain` - `image/<file type>` (for example, `image/png` or `image/jpeg`) **Size Limits** - Maximum request body: 5 MB - Effective maximum file size: ~3.5 MB (base64 encoding adds ~33% overhead) - Filename length: 5-64 characters **Re-upload Behavior** - Each document slot can only be filled once. The API rejects re-uploads to slots that already have a completed upload. - If you uploaded the wrong document, contact Evaluation Support. **Common Failure Scenarios** - Invalid or non-existent `subAccountRequestId` - Subaccount request is already `Approved` or `Denied` - Invalid `documentType` value - Missing or invalid data URI prefix in `base64data` - Unsupported MIME type - Document slot already has a completed upload - Non-admin user attempting to call the endpoint - Subaccount request belongs to a different organization - POA contact not found on the subaccount request **Next Steps** After uploading all three documents, use the `getpartnersubaccountrequeststatus` endpoint to check the status of the subaccount request.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.
subAccountRequestIdlongRequired
The requestId value returned from createpartnersubaccountrequest.
documentTypeenumRequired
The type of document being uploaded.
Allowed values:
filenamestringRequired5-64 characters

Filename for the document (5-64 characters).

base64datastringRequired<=8388608 characters

Document content as a base64-encoded data URI. Format must be data:<mime-type>;base64,<content>. Supported MIME types are application/pdf, text/plain, and image/*.

Response

SubmitPartnerSubaccountDocumentResponse
documentIdlong or null
Unique identifier for the uploaded document. Present on success.
errorTextstring or null
Error message if the upload failed.