Remerge Event Tracking API

Server-to-server ingestion API that Remerge clients and measurement partners use to forward data into the Remerge platform. A single GET endpoint at remerge.events/event accepts four documented payload families: in-app event data, attribution data (with is_attributed, click_id, campaign and rejection reasons), BI data flagged with non_app_event=true, and SKAdNetwork installs with decoded conversion values. Requests are authorized with a partner name and a Remerge-issued key passed as query parameters, and the endpoint answers HTTP 204 by default.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/remerge-event-tracking-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

API entry from apis.yml

apis.yml Raw ↑
aid: remerge-event-tracking-api
name: Remerge Event Tracking API
description: 'Server-to-server ingestion API that Remerge clients and measurement partners use to forward
  data into the Remerge platform. A single GET endpoint at remerge.events/event accepts four documented
  payload families: in-app event data, attribution data (with is_attributed, click_id, campaign and rejection
  reasons), BI data flagged with non_app_event=true, and SKAdNetwork installs with decoded conversion
  values. Requests are authorized with a partner name and a Remerge-issued key passed as query parameters,
  and the endpoint answers HTTP 204 by default.'
humanURL: https://help.remerge.io/hc/en-us/articles/6078711583260-Event-Data-Forwarding
baseURL: https://remerge.events
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/remerge.png
tags:
- Event
- Tracking
- Attribution
- Mobile
- SKAdNetwork
- Advertising
tags_raw:
- Events
- Tracking
- Attribution
- Mobile
- SKAdNetwork
- Advertising
properties:
- type: Documentation
  url: https://help.remerge.io/hc/en-us/sections/115000697994-API-Documentation
- type: APIReference
  url: https://help.remerge.io/hc/en-us/articles/6078711583260-Event-Data-Forwarding
- type: Authentication
  url: authentication/remerge-authentication.yml
- type: RateLimits
  url: rate-limits/remerge-rate-limits.yml
- type: Conventions
  url: conventions/remerge-conventions.yml
- type: DataModel
  url: data-model/remerge-data-model.yml
- type: Webhooks
  url: asyncapi/remerge-webhooks.yml