/update_record(RECON)

Cascades Reconciliation request received from Counterparty NP to Aarambh

Request Type: POST

Request Body: {"type":"RECON","data":<recon payload as mandated by ONDC>}

• type: Determines the type of record that is being sent to Aarambh

• data: recon payload schema as mandated by ONDC to be placed here.

Request Headers: {'authorization':'Authorization Signature generated','subscriberid':'ONDC transactional subscriber Id'}

Response:

1. Success Response : {"message":{"ack":{"status":"ACK"}}

2. Errors:

   1. data is not present: {"message":{"ack":{"status":"NACK"},"error":{"error":"Record data 'data' is missing"}}

   2. type is not present: {"message":{"ack":{"status":"NACK"},"error":{"error":"Record data 'type' is missing"}}

   3. other errors: {"message":{"ack":{"status":"NACK"},"error":{"error":"internal server error"}}

Determining INBOUND and OUTBOUND /recon

The /recon process in Aarambh operates in two directions: INBOUND and OUTBOUND. To facilitate seamless reconciliation, Aarambh introduces a requesttype header, which determines how the reconciliation request should be processed.

Flow Mechanism:

• OUTBOUND /recon: When Aarambh initiates an outbound reconciliation request, it includes the requesttype header in the API request.

  • The receiving Network Participant (NP) must check for the requesttype header.

  • If the header exists, the NP forwards the request to the Counterparty NP for further processing.

• INBOUND /recon: If the requesttype header does not exist, the NP must cascade the request back to Aarambh for reconciliation handling