v1.035

Sandbox receiving completion is now processed asynchronously.
Until now Complete Receiving (Sandbox) (POST /v1/integrations/sandbox/complete-receiving) simulated the whole receiving within the request, which failed with a 500 for large receivings once the request exceeded the server time limit. The endpoint now validates the request, moves the receiving to in_progress and queues the simulation; the 200 response means the receiving was accepted, not that it has been received.

🚀 New Endpoints

None

🛠 Schema & Property Updates

None

📦 New Support Schemas

None

📖 Documentation & Constraints Changes

• Complete Receiving (Sandbox) (POST /v1/integrations/sandbox/complete-receiving) — the simulation runs asynchronously. A 200 response means the receiving was accepted and moved to in_progress; the receiving_status_changed webhook with in_progress is sent right away. The result is visible via Retrieve Receiving (GET /v1/integrations/receiving, status received and received_at) or the Receiving status change webhook once the simulation finishes, which may take a few minutes for a large receiving.
• Complete Receiving (Sandbox) (POST /v1/integrations/sandbox/complete-receiving) — a receiving can be simulated only once. After the call, ShipMonk simulates the receiving process in the background, so the receiving stays in_progress while units are being received. You can follow the progress in the received quantities shown by Retrieve Receiving. Contact ShipMonk support only if the received quantities have stopped changing or you have been waiting for too long.

No endpoints, fields, or required-status were removed or changed. The response status code and body are the same, only the meaning of the 200 response changed from "received" to "accepted and queued", so this version stays backward-compatible for clients that read the receiving status afterwards.