Response Codes
This section describes all possible HTTP response codes from the vendor number assignment endpoint.
Status Codes
| Status Code | Description |
|---|---|
204 No Content | ✅ Success - The vendor number has been successfully assigned and the event status updated. |
400 Bad Request | ❌ Invalid request - The payload is malformed, signature is invalid, or the Id in the path doesn't match the Id in the body. |
404 Not Found | ❌ The onboarding request ERP event with the specified id was not found. |
500 Internal Server Error | ❌ Server error - An unexpected error occurred on the B1Link server. |
Success Response
Status: 204 No Content
No response body is returned on success. The vendor number has been successfully assigned and the onboarding request ERP event status has been updated.
Error Response Format
When an error occurs, the response may include a ProblemDetails object:
{
"type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
"title": "One or more validation errors have occurred.",
"status": 400,
"detail": "Invalid payload signature. The request signature does not match the expected signature.",
"instance": "/api/onboarding-request-erp-events/assign-erp-vendor-number-event"
}
Next Steps
- Error Handling - Detailed error scenarios and troubleshooting
- Testing - How to test your integration