AppsFlyer · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Engagements Impression Engagement API

3 actions 3 updates phrasing extends openapi/appsflyer-impression-engagement-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 3

$.info
$.paths['/impression/app/{platform}/{app_id}'].get
$.paths['/impression/app/{platform}/{app_id}'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Engagements Impression Engagement API
  version: 1.0.0
extends: openapi/appsflyer-impression-engagement-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: 2
- target: $.paths['/impression/app/{platform}/{app_id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Report an ad impression via GET
      effect: write
      questions:
      - How do I report an ad view to AppsFlyer as a query-string GET request?
      - Which parameters are required to log an impression by URL?
      instructions:
      - text: Report an impression for {app} on {platform} from media source {media_source} campaign {campaign} using the GET form.
        slots:
          app: path.app_id
          platform: path.platform
          media_source: query.af_media_source
          campaign: query.af_campaign_id
      - text: Send a GET impression for {app} on {platform} for ad {ad}, source {media_source}, campaign {campaign}.
        slots:
          app: path.app_id
          platform: path.platform
          ad: query.af_ad_id
          media_source: query.af_media_source
          campaign: query.af_campaign_id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/impression/app/{platform}/{app_id}'].post
  update:
    x-apievangelist-phrasing:
      intent: Report an ad impression via POST body
      effect: write
      questions:
      - Can I log view-through impressions server to server with a JSON body?
      - Can a posted impression carry the publisher site ID and device details?
      instructions:
      - text: Post an impression for {app} on {platform} from {media_source} campaign {campaign} in the request body.
        slots:
          app: path.app_id
          platform: path.platform
          media_source: requestBody.af_media_source
          campaign: requestBody.af_campaign_id
      - text: Post an impression body for {app} on {platform}, source {media_source}, campaign {campaign}, site {site}.
        slots:
          app: path.app_id
          platform: path.platform
          media_source: requestBody.af_media_source
          campaign: requestBody.af_campaign_id
          site: requestBody.af_siteid
      method: generated
      generated: '2026-10-01'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/appsflyer-impression-engagement-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.