Receive Vendor Dispatch Back
POST/api/repairs/vendor-dispatches/:dispatch/receive
Receive Vendor Dispatch Back.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Records the units that came back from the vendor (all or some). When some units are still out, the dispatch becomes partially_received, the message confirms how many were received (e.g. "1 unit received back from the vendor.") and missing_line_ids lists the units still with the vendor.
Request fields:
lines(required): array, min:1lines.*.line_id(required): integer, distinctlines.*.result(required): Enum:in:"repaired","unrepairable"lines.*.fee(optional): numeric, min:0, max:1000000lines.*.notes(optional): string, max:2000received_at(optional): date
Permission: repairs.vendor.
Authentication: Bearer token with the repairs:read / write scope.
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 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.