AppsFlyer · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Deep linking REST Android deep linking request API

2 actions 2 updates phrasing extends openapi/appsflyer-android-deep-linking-request-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for AppsFlyer's API. It is a proposal applied on top of the contract, not a document AppsFlyer publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 2

$.info

$.paths['/android/{app_id}'].post

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Deep linking REST Android deep linking request API
  version: 1.0.0
extends: openapi/appsflyer-android-deep-linking-request-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 1
- target: $.paths['/android/{app_id}'].post
  update:
    x-apievangelist-phrasing:
      intent: Resolve a deep link for an Android app open
      effect: read
      questions:
      - How do I get deep link data for an Android install without the SDK?
      - Can I pass Google Play referrer strings to resolve deferred deep linking?
      - What device details are required for an Android deep link request?
      instructions:
      - text: Resolve the Android deep link for app {app} on first launch from IP {ip} at {timestamp}.
        slots:
          app: path.app_id
          ip: requestBody.ip
          timestamp: requestBody.timestamp
      - text: Request Android deep link data for {app} with referrers {referrers} and signature {sig}.
        slots:
          app: path.app_id
          referrers: requestBody.referrers
          sig: query.af_sig
      method: generated
      generated: '2026-10-01'