Remerge

Remerge is a mobile demand-side platform (DSP) specializing in app retargeting, re-engagement, and user acquisition for mobile apps. The Berlin-based company (Remerge GmbH) helps advertisers in gaming, e-commerce, and delivery build in-app audience segments, run programmatic re-engagement and acquisition campaigns across millions of ad placements, and validate results with incrementality measurement. Onboarding is account-managed rather than self-service, but Remerge does publish two documented HTTP APIs: a JSON Reporting API at api.remerge.io for pulling daily campaign performance into a client's BI stack, and an Event Tracking API at remerge.events for forwarding in-app event, attribution, BI and SKAdNetwork data into Remerge. It operates an ISO/IEC 27001:2022-aligned ISMS and publishes a public Trust Center and vulnerability disclosure policy.

Remerge publishes 2 APIs on the APIs.io network. Tagged areas include Company, Advertising, AdTech, Mobile, and Retargeting.

The Remerge catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Remerge’s developer surface includes support, engineering blog, documentation, API reference, authentication, and 21 more developer resources.

🌐 Visit website 📡 Source on GitHub

44.7/100 developing ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

2 APIs

Company Advertising AdTech Mobile Retargeting Demand-Side Platform User Acquisition Marketing

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 44.7/100 · developing

Contract Quality 10.4 / 25

Developer Ergonomics 9.0 / 20

Access Clarity 8.7 / 20

Operational Transparency 6.8 / 13

Contract Governance 2.2 / 12

Discoverability 7.6 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/remerge: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Remerge Reporting API

JSON reporting API that lets Remerge advertisers pull daily (or hourly) campaign performance for their active campaigns into their own BI systems. A POST to /report with a start...

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

Pricing Plans 1

Published pricing tiers and plan structures.

Remerge Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Remerge Rate Limits

3 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Remerge Webhooks

ASYNCAPI

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Remerge Authentication

http/apiKey · 2 schemes

SECURITY

Remerge Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Remerge Vulnerability Disclosure

contact published

SECURITY

Remerge Trust Center

ISO 27001, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

DataModel

Lifecycle

Conformance

Webhooks

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Compliance

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: remerge
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/remerge.png
name: Remerge
description: 'Remerge is a mobile demand-side platform (DSP) specializing in app retargeting, re-engagement, and user acquisition
  for mobile apps. The Berlin-based company (Remerge GmbH) helps advertisers in gaming, e-commerce, and delivery build in-app
  audience segments, run programmatic re-engagement and acquisition campaigns across millions of ad placements, and validate
  results with incrementality measurement. Onboarding is account-managed rather than self-service, but Remerge does publish
  two documented HTTP APIs: a JSON Reporting API at api.remerge.io for pulling daily campaign performance into a client''s
  BI stack, and an Event Tracking API at remerge.events for forwarding in-app event, attribution, BI and SKAdNetwork data
  into Remerge. It operates an ISO/IEC 27001:2022-aligned ISMS and publishes a public Trust Center and vulnerability disclosure
  policy.'
url: https://raw.githubusercontent.com/api-evangelist/remerge/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- point-nine
x-tier: profiled
x-tier-reason: 'Upgraded from stub 2026-08-12: two documented public HTTP APIs were found and registered. The earlier "no
  public developer API" reading was wrong — the contract discovery step surfaced the Reporting API and Event Tracking API
  in the Zendesk Help Center''s Developer Documentation category.'
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-12'
tags:
- Company
- Advertising
- AdTech
- Mobile
- Retargeting
- Demand-Side Platform
- User Acquisition
- Marketing
apis:
- aid: remerge-reporting-api
  name: Remerge Reporting API
  description: JSON reporting API that lets Remerge advertisers pull daily (or hourly) campaign performance for their active
    campaigns into their own BI systems. A POST to /report with a start_date and end_date returns a results array aggregated
    across up to seven dimensions (audience, country, campaign, campaign_type, ad, ad_label, platform) with impressions, clicks,
    cost, conversions, attributed conversions, app-open rate and unique users. Authorization is a token obtained from a sign-in
    request against the same host using dashboard credentials. Remerge retains reportable data for six months only.
  humanURL: https://help.remerge.io/hc/en-us/articles/115003440434-Remerge-Reporting-API
  baseURL: https://api.remerge.io
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/remerge.png
  tags:
  - Reporting
  - Analytics
  - Advertising
  - AdTech
  - Campaigns
  - Business Intelligence
  properties:
  - type: Documentation
    url: https://help.remerge.io/hc/en-us/sections/360003940000-Reporting-API
  - type: APIReference
    url: https://help.remerge.io/hc/en-us/articles/115003440434-Remerge-Reporting-API
  - type: Authentication
    url: authentication/remerge-authentication.yml
  - type: RateLimits
    url: rate-limits/remerge-rate-limits.yml
  - type: ErrorCatalog
    url: errors/remerge-problem-types.yml
  - type: Conventions
    url: conventions/remerge-conventions.yml
  - type: DataModel
    url: data-model/remerge-data-model.yml
- 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
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.remerge.io
- type: Support
  url: https://help.remerge.io/hc/en-us
- type: Blog
  url: https://www.remerge.io/blog-post
- type: GitHubOrganization
  url: https://github.com/remerge
- type: PrivacyPolicy
  url: https://www.remerge.io/service-privacy-policy
- type: TermsOfService
  url: https://www.remerge.io/terms-and-conditions
- type: TrustCenter
  url: security/remerge-trust-center.yml
- type: Compliance
  url: https://trust.remerge.io/
- type: VulnerabilityDisclosure
  url: security/remerge-vulnerability-disclosure.yml
- type: Security
  url: https://www.remerge.io/remerge-vulnerability-disclosure-policy
- type: DomainSecurity
  url: security/remerge-domain-security.yml
- type: LLMsTxt
  url: llms/remerge-llms.txt
- type: DeveloperPortal
  url: https://help.remerge.io/hc/en-us/categories/115000321013-Data-Exchange
- 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/115003440434-Remerge-Reporting-API
- type: Login
  url: https://admin.remerge.io
- type: Authentication
  url: authentication/remerge-authentication.yml
- type: RateLimits
  url: rate-limits/remerge-rate-limits.yml
- type: ErrorCatalog
  url: errors/remerge-problem-types.yml
- type: Conventions
  url: conventions/remerge-conventions.yml
- type: DataModel
  url: data-model/remerge-data-model.yml
- type: Lifecycle
  url: lifecycle/remerge-lifecycle.yml
- type: Packages
  url: packages/remerge-packages.yml
- type: Conformance
  url: conformance/remerge-conformance.yml
- type: Plans
  url: plans/remerge-plans-pricing.yml
- type: Webhooks
  url: asyncapi/remerge-webhooks.yml
x-coverage:
  state: covered
  checked: '2026-08-12'
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 11
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/remerge"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/remerge/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/remerge/evidence"

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.

GitHub Google LinkedIn

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