Can AI agents automate AppsFlyer?

AppsFlyer is automatable today through its documented APIs. Admins create tokens in Security Center. An API V2 JWT authorizes calls such as Pull API, Cohort, ROI, Master API, and audience import. A separate OneLink token authorizes the OneLink REST API, which creates, reads, updates, and deletes short links. An S2S token authorizes mobile and web server-to-server events. Only admins can manage tokens, and admins can hold at most two tokens of each type. OneLink API v2.0 is the current version. The overview page says v1 will sunset on June 1, 2026. UI, bulk, and SDK-created links cannot be updated or deleted through OneLink API v2.0. AppsFlyer also hosts a beta MCP server at https://mcp.appsflyer.com/auth/mcp. Browser OAuth lasts about 7 days. Automation clients send an MCP token as Authorization Bearer. The server is read and query only. An admin can disable it under Account and Profile, AI capabilities. Official SDKs are documented for Android, iOS, Unity, React Native, Flutter, and other app platforms. Zapier, Make, Power Automate, and n8n were not assessed. No AppsFlyer CLI was opened. Computer-use viability is unassessed. API and MCP each score 6. API is the best path because token-authenticated calls can create links and send events, while the MCP server cannot change AppsFlyer.

Best path today: api · Overall automatability: 6/10