Bulk Process ShipMyOrders Invoices
POST/api/shipmyorders/invoices/process
Processes several ShipMyOrders invoices. Processing walks every line of the invoice: it applies the first matching nominal-code mapping rule, then looks for a SKU.io fulfillment whose number equals the line reference. When one is found, a Fulfillment cost line (quantity, amount, tax from the invoice line; allocated to products by revenue) is added to that fulfillment's sales order and linked to the invoice line. Lines without a matching fulfillment only receive their nominal code. The invoice's processed_at is then set.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Body: ids (array of invoice ids, required, at least one; each must exist).
Returns the processed invoices. Lines (items) are not included in this response.
Requires the integrations.update permission.
Authentication: Bearer token (Personal Access Token).
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
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.
Unprocessable Entity
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.