Which or APTRA platform edition you are deploying on.
Encrypt all inbound and outbound host communications using TLS 1.3 to prevent man-in-the-middle packet manipulation.
# Sample Docker run command from the guide docker run -d \ --name aptra-advance-ndc \ -p 8080:8080 \ -e NDC_AGGREGATOR_TYPE=DUFFEL \ -e DUFFEL_API_KEY=sk_test_xxxx \ -e LOG_LEVEL=DEBUG \ ncr/aptra-advance:ndc-latest aptra advance ndc developer-s guide
APTRA Advance NDC allows developers to inject custom logic into the state machine using dynamic link libraries (DLLs) written in C++ or C#. To implement a custom state:
"selectedOfferID": "OFF-JFK-LHR-001", "passengerDetails": [ "firstName": "John", "lastName": "Doe", "dob": "1985-04-12" ], "contactInfo": "email": "john@example.com", "phone": "+123456789" Which or APTRA platform edition you are deploying on
"type": "https://api.aptra-advance.com/errors/offer-expired", "title": "Offer Expired", "status": 409, "detail": "Offer OFF-JFK-LHR-001 cannot be booked after its TTL of 240 seconds.", "instance": "/ndc/order", "retryAfter": 0
Re-initialize the security keys from the Host or check the EPP security configuration policies. Misconfigured FIT or State Type A parameters. The signature is an HMAC-SHA256 of the raw
POST /auth/token Host: api.aptra-advance.com Content-Type: application/x-www-form-urlencoded
print(f"Booking created: order_id")
The guide mandates that you validate the X-APTRA-Signature header on every incoming webhook. The signature is an HMAC-SHA256 of the raw payload, using your tenant secret as the key.
When working on an APTRA Advance NDC deployment, developers typically interact with the following core directories (paths may vary slightly depending on the specific APTRA runtime version):