Complete Request Examples
This section provides complete working examples of requests to the vendor number assignment endpoint.
cURL Example
curl -X PUT \
'{baseUrl}/api/onboarding-request-erp-events/assign-erp-vendor-number-event' \
-H 'Content-Type: application/json' \
-H 'X-B1LINK-Signature: <computed-signature>' \
-d '{
"Id": "550e8400-e29b-41d4-a716-446655440000",
"ErpVendorNumber": "VENDOR-12345"
}'
HTTP Request
PUT {baseUrl}/api/onboarding-request-erp-events/assign-erp-vendor-number-event HTTP/1.1
Content-Type: application/json
X-B1LINK-Signature: <computed-signature>
Content-Length: 89
{
"Id": "550e8400-e29b-41d4-a716-446655440000",
"ErpVendorNumber": "VENDOR-12345"
}
Response
Success Response
Status: 204 No Content
No response body is returned on success.
Error Response
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
- Response Codes - Understand all possible response codes
- Error Handling - Learn how to handle errors
- Code Examples - See implementation examples in your preferred language