Skip to content
WebsiteLogin

API reference and fraud reasons

Choose the reference for your task. The Admin API manages settings and reports. The three gateway APIs screen traffic through separate GET operations with query parameters and service-specific responses.

The Admin snapshot uses api.app.24metrics.com/api/v2. Follow each operation’s authentication requirements: the specification defines the API-KEY header and Authorization Bearer schemes. Do not apply those credentials to gateway requests.

Original source: Reports and Admin Management API docs.

Use your integration’s generated gateway host, not the Admin host. The snapshots use integration-id.gateway.go2link.co as a placeholder. Gateway requests do not use an Admin API key or Bearer token. Click and conversion requests use separate conditional secure codes; impressions do not use click secrets. Keep secure codes and any separate click signing key on your backend.

Responses are not universally JSON or synchronous decisions. Follow each service’s documented status codes, content formats, and error handling. The Conversion API creates conversions; click lookup and rejection updates are separate workflows outside these three snapshots.

For setup and backend request guidance, see API integration. The original API integration documentation remains available as external provenance; the local references preserve the supplied service contracts.

When a response includes a rejection reason, use the matching service table. Not every response contains a reason field.