Title Indigo Search API – Troubleshooting ✅

Indigo Search API – Troubleshooting Use this guide when a search request behaves unexpectedly. Each section points to the relevant Java classes so you can verify behaviour quickly. 1. Retrieve the Raw Supplier Payload 1. Search the logs for your UUID: grep "X-SEARCH-ID=" logs/*.log 2. Copy the xmlSearchLogsKey printed by SearchController. 3. Pull the stored XML pair from Redis (requires local redis-cli access): redis-cli GET _ 4. Replay the request in Postman or curl to confirm whether Navitaire returned an error or empty availability. 2. Signature or Session Problems Symptoms: Repeated messages like Session token authentication failure. What to check: ● SearchController.RecallSearchWithSession(...) should be invoked automatically; confirm the retry happens. ● Ensure the scheduled job that refreshes SignatureSheduler is running; if not, log in manually through the session endpoint. ● For affiliate searches, verify credentials.indigo.agentName/password are present — without them Navitaire rejects the logon.


☑ Promotion code verified against configuration ☑ Airport codes and domestic flags double-checked ☑ Reissuance filters inspected for direction mismatches ☑ Downstream event consumers monitored for delivery issues Capture these findings in your ticket or hand-off notes — it saves a round-trip for the next person investigating the same problem.