Remerge

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.

GitHub

Documentation

📖
Documentation
https://help.remerge.io/hc/en-us/sections/115000697994-API-Documentation
📖
APIReference
https://help.remerge.io/hc/en-us/articles/6078711583260-Event-Data-Forwarding
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/remerge/refs/heads/main/authentication/remerge-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/remerge/refs/heads/main/rate-limits/remerge-rate-limits.yml

Other Resources

🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/remerge/refs/heads/main/conventions/remerge-conventions.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/remerge/refs/heads/main/data-model/remerge-data-model.yml
🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/remerge/refs/heads/main/asyncapi/remerge-webhooks.yml

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:
- 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