Replace EDI Document Content
POST/api/spscommerce/:integrationInstance/documents/:document/replace-content
Replace an unreadable warehouse shipping advice (945) with a corrected file and queue it to be applied. Send multipart/form-data with a file field of at most 5 MB. The unreadable file is kept with the document. Every usual check still runs, including the sender check, so a replacement can't record what a resend couldn't.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token and the integrations.update permission.
Returns 422 when the document isn't an unreadable 945 or the file isn't a readable 945, and changes nothing; 404 when it belongs to another connection.
Request
Responses
- 202
- 401
- 403
- 404
- 422
- 429
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.