Status code 401 Unauthorized

Description The consumer must pass a valid access token in the Authorization HTTP header for each request to a secure resource.

The WWW-Authenticate HTTP response header is also present compliant with the OAuth2 specification.

POST /enterprises

If no access token was provided in the request’s Authorization HTTP header, the service returns:

HTTP/1.1 401 Unauthorized
Content-Type: application/problem+json
WWW-Authenticate: Bearer realm="example"

{
   "type": "urn:problem-type:belgif:noAccessToken",
   "href": "https://www.belgif.be/specification/rest/api-guide/problems/noAccessToken.html",
   "status": 401,
   "title": "No Access Token",
   "detail": "No Bearer access token found in Authorization HTTP header"
}