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 is listed with 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 📡 Profile data on GitHub

46.8/100 developing ▬ flat Agent 25/100 agent aware Front door AI 1/6 silent Heartbeat 69/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs

Company Advertising AdTech Mobile Retargeting DSP User Acquisition Marketing

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 46.8/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 7.7 / 17

Access Clarity 7.4 / 17

Operational Transparency 5.8 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 5.3 / 15

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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/remerge/"><img src="https://apis.io/badge/remerge/card.svg" alt="Remerge on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 43.4 — up to +11.3 composite points
Developer Ergonomics scores 45.2 — up to +11.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/remerge/apis.yml: open an issue on github.com/api-evangelist/remerge to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	covered	35.8 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dataspace Protocol

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

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

Remerge API pricing

Rate limits

Reporting API concurrent queries: 1 concurrent requests
Reporting API query interval ceiling: 14 query window days
Event Tracking API request rate: 1000 requests per second

Rate-limit details →

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

FinOps 1

Cost, billing, and metering signals for API financial operations.

Remerge Finops

FINOPS

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
  probe_state: covered
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  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
- DSP
- User Acquisition
- Marketing
tags_raw:
- Company
- Advertising
- AdTech
- Mobile
- Retargeting
- Demand-Side Platform
- User Acquisition
- Marketing
apis:
- aid: remerge: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: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

Remerge API — frequently asked questions

Does Remerge have an API?

Yes. APIs.io lists 2 APIs from Remerge, including Remerge Reporting API and Remerge Event Tracking API.

How do I authenticate with the Remerge API?

Remerge uses bearer-token authentication (http/apiKey · 2 schemes). The details are profiled on APIs.io as Remerge Authentication.

Is the Remerge API ready for AI agents?

Remerge has a Kin Score of 46.8 out of 100 (developing) and an Agent Readiness score of 25.2 (agent-aware), scored by API Evangelist on 2026-11-06.

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"

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.

GitHub Google LinkedIn

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