Sender receives the status answer
Hosted by every participant that sends /v1/status.
The exchange posts this message to the endpoint_URL you registered, at /v1/on_status, with the headers and the sealed payload the sender posted. Answer HTTP 202 with the receipt first and process afterwards; Receiving a callback has the rules.
The answer to a status request, delivered to the sender that asked. The Every NHCX call carries the access token from the session call in a header named Example These fields go in the JWE protected header of Key management algorithm. Always Example Content encryption algorithm. Always Example Your participant code. Mandatory on the envelope. Example The recipient's. For a provider, the processor code from the policy lookup. Mandatory on the envelope. Example Fresh on every message, including responses. Mandatory on the envelope. Example The thread that ties a request to its answers. The correlation ID rule says when to reuse it. Mandatory on the envelope. Example The time the message was made. Timestamp gives the format. Mandatory on the envelope. Example Where this message stands. Status words lists the values. Mandatory on the envelope. Example Always One of Received. The receipt names the message it answers; the answer itself follows as a call of your own.x-hcx-status in the protected header says where the message you asked about got to. The payload is an empty string.Authorizations
bearer_authapiKeyRequiredbearer_auth, as the word Bearer, a space and the token. NHCX reads bearer_auth, not Authorization.Bearer <access token>Protected header
payload, not as HTTP headers. Building and sending a JWE shows how to prepare and encrypt the payload, and Receiving a callback how to decrypt one.algstringRequiredRSA-OAEP-256: the content key is wrapped with the recipient's RSA public key.RSA-OAEP-256encstringRequiredA256GCM.A256GCMx-hcx-sender_codestringRequired<participant code>x-hcx-recipient_codestringRequired<recipient code>x-hcx-api_call_idstringRequired<uuid>x-hcx-correlation_idstringRequired<correlation id>x-hcx-timestampstringRequired<iso timestamp>x-hcx-statusstringRequiredresponse.completeBody
typestringRequiredJWEPayload. Every response (on_) call sends it beside payload.JWEPayloadpayloadstringRequiredResponses
202timestampstringapi_call_idstringcorrelation_idstringresultobjectresult.sender_codestringresult.recipient_codestringresult.entity_typestringresult.protocol_statusstringerrorobjecterror.codestringerror.messagestring
Where this fits
NHCX delivers this message to the participant when the recipient calls /v1/on_status: Recipient: answer a status check.