Amadeus API Flight Data Consultation -- 2

I am adding Amadeus’ enterprise SOAP services to an existing Node.js back-end and want your seasoned guidance before I dive any deeper. The immediate goal is to wire up the Flight Information endpoints—specifically schedules, real-time status, and availability—so that my service can request and parse those responses reliably in production.

Here is what I need from you:

• A concise walkthrough of the correct WSDLs, credentials flow, and required headers for the Flight Information APIs.
• Best-practice Node.js patterns (axios/soap module, async error handling, XML-to-JSON mapping) that you have already battle-tested with Amadeus.
• Sample calls that pull schedules, real-time status, and availability, along with an explanation of the key response fields so I can map them into my existing data model.
• Advice on performance considerations (caching, rate limits, retries) and any Amadeus quirks you have encountered.

Acceptance criteria
1. I can run your sample Node.js script, swap in my credentials, and successfully retrieve each of the three flight data sets.
2. You have answered all open questions around authentication, endpoint selection, and error scenarios during a live call or well-documented hand-off.

If you have demonstrable experience integrating Amadeus SOAP endpoints in Node, let’s talk so I can move forward with confidence.