Srikar Chamarthy
02/25/2026, 5:46 PMkapa.ai
02/25/2026, 5:46 PMapi_token, app_id, start_date, timezone), but they do not document the internal URLs or how aggregate endpoints like daily_report/v5 are called. [AppsFlyer source] Because of that, I cannot reliably tell from the provided knowledge whether:
• the path /api/agg-data/export/app/id154/daily_report/v5 is correct for your app/account,
• the date range or timezone parameters are acceptable to AppsFlyer, or
• this is a temporary AppsFlyer-side issue.
What you can do within Airbyte, based on the documented error‑handling features:
1. Treat 404 as a handled condition (if you are building or editing the connector):
In a config‑based connector YAML, you can add a response filter to either retry or ignore 404s:
requester:
# ...
error_handler:
response_filters:
- http_codes: [404]
action: IGNORE # or RETRY
[Config error handling]
This won’t fix a wrong URL, but it will prevent the sync from failing if 404s are expected for some date ranges or resources.
2. If you are using the Connector Builder UI, you can configure a response filter on HTTP codes and set 404 with an appropriate action (e.g., IGNORE or RETRY), so the sync doesn’t hard‑fail on that status. [HTTP Codes]
However, to actually resolve the 404 (rather than just handling it), you will need to verify the AppsFlyer API URL and parameters against AppsFlyer’s own API documentation or test the URL directly outside Airbyte. The Airbyte knowledge sources provided do not contain enough detail about AppsFlyer’s aggregate export endpoints to say what exactly is wrong with this specific URL. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.