Skip to main content
POST
cURL

Overview

The Global Event Postback API fires a conversion or tracking event across all campaigns within an organization using a single endpoint. It is designed for buyers and third-party systems that receive leads from multiple campaigns but want to post conversion data back using one consistent URL — without needing a different endpoint per campaign. Pingtree resolves the campaign and lead from the transaction_id automatically. No cid is required in the request body.

Endpoint

Replace {org-id} with your organization’s unique ID (available in your Pingtree dashboard under account settings).

Authentication

No token-based authentication header is required. The org-id path parameter scopes the request to your organization.

Request Parameters

Path Parameters

Body Parameters (JSON)

Example Request

Non-Conversion Event

Example Responses

Success — Conversion Event Fired

Success — Tracking Event Fired

Error — Missing Event ID

Error — Missing Transaction ID

Error — Lead Not Found

Error — Invalid Event ID

Error — Duplicate Event

Status Codes

Comparison with Campaign-Specific Event Postback

Tips

  • Preferred endpoint for buyers. If you are a buyer receiving leads from multiple campaigns within the same organization, use this global endpoint to avoid managing per-campaign event URLs.
  • Event ID must exist in the matched campaign. Even though you do not pass a cid, Pingtree resolves the campaign from the transaction_id. The event_id must be configured in that campaign’s event settings.
  • Revenue is required for conversion events. If the matched event is a conversion type, omitting revenue returns a 400 error.
  • Deduplication. If the campaign event has duplicate conversion disabled, sending the same event_id + transaction_id a second time returns a 400 duplicate error.
  • Postback URL format. When configuring this as a server-to-server postback URL in a third-party platform, use a template like: https://api.pingtree.com/api/event/global/org_5f1a2b3c?event_id=sale_completed&transaction_id={transaction_id}&revenue={payout}

Path Parameters

org-id
string
required

Your organization ID

Body

application/json

Lead details to add to the campaign

transaction_id
string
required

Lead's Transaction ID, Which was generate from click script of Pingtree

event_id
string
required

Event ID which you want to fire for the lead

clid
string

clid of the offer

amount
number

Amount is conversion amount for lead

pid
string

PID is partner ID

conversion_date
string

conversion_date should be as following, 'YYYY-MM-DD' or 'YYYY-MM-DD HH:MM:SS'

conversion_timezone
string

conversion_timezone should be as following, 'PST'(For Pacific Stand Time (UTC-8)), 'EST'(For Eastern Standard Time (UTC-5)), 'CST'(For Central Standard Time (UTC-6)), 'MST'(For Mountain Standard Time (UTC-7)), 'AKST'(For laska Standard Time (UTC-9)), 'SST'(For Samoa Standard Time (UTC-11)), 'HST'(For Hawaii-Aleutian Time (UTC-10)), 'AST'(For Atlantic Standard Time (UTC−4)

sub1
string

Sub ID 1 of lead's partner tracking URL

sub2
string

Sub ID 2 of lead's partner tracking URL

sub3
string

Sub ID 3 of lead's partner tracking URL

sub4
string

Sub ID 4 of lead's partner tracking URL

sub5
string

Sub ID 5 of lead's partner tracking URL

adv1
string

Adv ID 1 of lead's partner tracking URL

adv2
string

Adv ID 2 of lead's partner tracking URL

adv3
string

Adv ID 3 of lead's partner tracking URL

adv4
string

Adv ID 4 of lead's partner tracking URL

adv5
string

Adv ID 5 of lead's partner tracking URL

utm_source
string

UTM Source of lead's partner tracking URL

utm_medium
string

UTM Medium of lead's partner tracking URL

utm_campaign
string

UTM Campaign of lead's partner tracking URL

utm_adgroup
string

UTM AdGroup of lead's partner tracking URL

utm_matchtype
string

UTM MatchType of lead's partner tracking URL

utm_term
string

UTM Term of lead's partner tracking URL

utm_content
string

UTM Content of lead's partner tracking URL

external_clickid
string

External Click ID of lead's partner tracking URL

utm_creative
string

UTM Creative of lead's partner tracking URL

utm_placement
string

UTM Placement of lead's partner tracking URL

TCPA Consent Date in YYYY-MM-DD format

TCPA consent field as 0 or 1

cost
number

Cost of the lead

cost_operation
string

Cose Operation for of the lead's cost. Possible values are 'add', 'substract', and 'override'.

adSpend
number

Adspend of the lead

min_price
number

Send minimum buying price to buyer, if buyer is ready to buy lead at min price or greater, then only we will sell lead

{key}

You can send any other lead details like first_name, last_name, address, etc. You can find all lead fields in the 'Field Management' Page inside your Pingree account.

Response

Event successfully fired

status
string

Status code of API response

type
string

Type of API response which can be success or error

message
string

Message of API response

missingFields
object

Missing lead's fields

invalidFields
object

Missing lead's fields