Push Expected Arrival To Veracore
POST/api/veracore/integration-instances/:integration_instance/expected-arrivals/push
Announce a SKU.io purchase order to Veracore as an expected arrival.
The announcement is assembled and validated synchronously so blocking problems — an unmapped product, an unmapped warehouse, a missing arrival date — come back on this request rather than failing later in the background. When it passes, the send is queued and progress is reported against the returned tracked_job_log_id. Re-pushing the same purchase order refreshes the existing announcement instead of creating a second one.
An expected arrival is an announcement, not a receipt: pushing one tells the warehouse what is coming, it never adds stock. Every quantity here is expected. Once Veracore marks an arrival received it can no longer be edited or cancelled through the API, which is what is_locked reflects.
Body fields
purchase_order_id(integer, required) — SKU.io purchase order to announce. Must reference an existing purchase order.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
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.