application/problem+json. Base your error handling on code, which doesn’t change. title and detail are written for people and may be reworded. When Orchestrator knows more about a particular error, such as why a token was rejected or when to retry, detail says so.
422 can have several causes, so it also lists each one in errors, with a detail and, when the cause is tied to a field, a pointer to that field as a JSON Pointer:
401 also carries a WWW-Authenticate: Bearer header, as defined in RFC 6750, with error="invalid_token" when a token was sent but rejected.
A
502, 503 or 504 comes from the load balancer in front of Orchestrator, not from Orchestrator itself, and has no JSON body.