Report sales from padi links with the Offers events API

Your server tells us what happened on your side: purchases, signups and refunds. We record a conversion for the padi who sent you the customer, and you can reconcile what you sent against what we recorded and charged.

Overview

An offer is a pay-per-conversion link campaign. You fund a number of conversions, padis share tracked links, and you pay only for the customers who complete the action the offer pays for. This page is for the developer who connects your shop or app to it.

Send every purchase to the events API, not just the ones with a click id. Sales from padis become conversions. The rest are stored as unattributed, which is what lets the reconciliation report show your share of sales from padis.

Base URL
https://api.opinionpadi.com/api/v1/offers
Authentication
Authorization: Bearer op_sk_live_...
Format
JSON in and out. Amounts in naira by default.
Rate limit
600 requests a minute per key. A batch is one request.

How it works

  1. 1

    A padi shares their link

    Each padi on your offer gets a short link such as https://opbio.link/TOLU7X. A customer opens it.

  2. 2

    The customer lands on your site

    We count the click and redirect to your offer's destination URL with op_click (the click id) and op_ref (the padi's code) added.

  3. 3

    Your site keeps op_click

    A small script stores it in a first-party cookie so it is still there when the customer pays or signs up.

  4. 4

    Your server sends an event

    When the order is paid, your server sends a purchase (or signup, lead and so on) with the stored click_id and your own event_id.

  5. 5

    A pending conversion is recorded

    On a live key, an attributed event becomes a pending conversion and its cost is reserved from the offer budget.

  6. 6

    The hold ends and the padi is paid

    The conversion pays the padi when the offer's hold ends. Until then you can refund it, or reject it in the dashboard. On a 0-day hold it pays at once.

Landing URL after the redirect
https://shop.example.ng/signup?src=ads&op_click=01JBZ7Q4M2X8RC5T9VK3NHW6AE&op_ref=TOLU7X&utm_source=opinionpadi&utm_medium=offers&utm_campaign=offer-42

Your own query string and fragment are kept. utm_* values are added only when your URL does not already set them.

Refunds

A full refund sent inside the hold reverses the pending conversion, and its cost goes back to the offer. Once a conversion has paid, it is final.

Reconciliation

The reconciliation report lines up the events you sent against the conversions we recorded and lists every mismatch with what to do about it.

Quickstart

Two pieces: a script on your site that keeps the click id, and a call from your server when the order is paid. Start with a test key so nothing is charged while you build.

1. Keep op_click in the browser

Add the browser build of @opinionpadi/offers to every page a padi link can land on. It stores op_click and op_ref in first-party cookies (named the same) for 30 days. Set data-days to at least your offer's attribution window. It never needs your secret key. The latest padi link wins: a new link replaces both values.

HTML
<!-- On every page a padi link can land on. Stores op_click and op_ref
     from the URL in first-party cookies when the page loads. -->
<script src="https://unpkg.com/@opinionpadi/offers@0.1.0/dist/opinionpadi.js"
        data-days="30" defer></script>
JavaScript
// Or, if you bundle your front end:
import { capture, getAttribution } from "@opinionpadi/offers/browser";

capture({ days: 30 });           // on every page load
const { click_id, ref } = getAttribution();   // at checkout, if you post it yourself

2. Send the event from your server

Read the cookie when the order is paid and send a purchase. Use your order number as event_id: retries with the same id never count twice.

# Your server, after the order is paid.
# click_id is the op_click cookie value from the customer's browser.
curl https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer $OPINIONPADI_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "purchase",
    "event_id": "order_10023",
    "click_id": "01JBZ7Q4M2X8RC5T9VK3NHW6AE",
    "amount": 15000.50,
    "customer_id": "cust_9"
  }'

3. Check the result

The response has an outcome. With a click id on a live key you should see converted and a conversion with status pending. Without one you will see unattributed, which is expected for sales that did not come through a padi. With a test key, nothing is recorded and the conversion is marked "simulated": true. See test mode.

Keep keys on your server

Secret keys can record conversions that you pay for. Never put one in a browser, a mobile app or a public repository. The browser only ever handles op_click and op_ref.

Install an SDK

The SDKs wrap every call on this page with the same method names in each language, retry safely, and read the attribution cookies for you. They have no runtime dependencies. You can also call the HTTP API directly, as the curl examples do.

npm install @opinionpadi/offers
  • Node.js 18+ and the browser
    Package:
    @opinionpadi/offers
    Import
    import { OpinionPadi } from '@opinionpadi/offers'
  • PHP 8.1+
    Package:
    opinionpadi/offers
    Import
    use OpinionPadi\Offers\OpinionPadi;
  • Python 3.9+
    Package:
    opinionpadi-offers
    Import
    from opinionpadi_offers import OpinionPadi

Create a client

export OPINIONPADI_SECRET_KEY="op_sk_test_..."

curl https://api.opinionpadi.com/api/v1/offers/account \
  -H "Authorization: Bearer $OPINIONPADI_SECRET_KEY"

Authentication and keys

Send your secret key as a bearer token on every request. Create keys on the Developers page of the business dashboard. The secret is shown once, so copy it when you create it. You can hold up to 10 active keys and revoke any of them there. A revoked key gets 401 api_key_revoked from then on.

Header
Authorization: Bearer op_sk_live_...
  • Live
    Prefix:
    op_sk_live_
    What it does
    Records real conversions. Conversions are paid from your offer budgets. Creating one emails your business account.
  • Test
    Prefix:
    op_sk_test_
    What it does
    Same validation and attribution, but nothing is recorded against an offer and no money moves. Each event says what a live event would have done.

These keys are separate from the API key on the Settings page that the Clout Orders API uses. Each mode keeps its own events, so the same event_id can exist once in test and once in live.

Check a key

GET /account confirms the key works and lists your offers (up to 100, newest first) with the event type each one pays for, its payout, unit cost, hold days and whether the integration is verified. Test keys also get the list of test values.

Response 200
{
  "object": "account",
  "business": { "id": 7, "name": "Mama Put Foods" },
  "key": { "name": "Shop server", "mode": "test" },
  "offers": [
    {
      "id": 42,
      "title": "First order on Mama Put",
      "status": "approved",
      "event_type": "purchase",
      "conversion_event": "First order",
      "payout_amount": 800,
      "unit_cost": 960,
      "hold_days": 7,
      "attribution_window_days": 30,
      "integration_verified": true
    }
  ],
  "test_values": ["op_test_converted", "op_test_converted_paid", "op_test_budget_exhausted", "op_test_outside_window", "op_test_offer_closed", "op_test_link_blocked", "op_test_fraud", "op_test_unknown"]
}

POST /events

Send an event

One event per thing that happened on your side. Without click_id or ref the event is unattributed: stored for reconciliation, never a conversion.

  • type
    Required:
    Yes
    Description
    purchase, signup, lead, install, subscription, custom or refund.
  • event_id
    Required:
    Yes
    Description
    Your own id for this event, up to 191 characters: the order number or signup id. Unique per key mode. Sending the same event_id again returns the first result and changes nothing.
  • click_id
    Required:
    No
    Description
    The op_click value from the landing URL. Preferred.
  • ref
    Required:
    No
    Description
    The padi's code (op_ref), if that is what you stored. Case-insensitive.
  • offer_id
    Required:
    No
    Description
    Your offer's id. Optional with click_id or ref, since they identify the offer, and checked against them when sent. Useful on unattributed events so they show in that offer's reconciliation.
  • amount
    Required:
    No
    Description
    Order value in naira, up to 2 decimal places. Used for reconciliation and reports, never for what a conversion costs.
  • currency
    Required:
    No
    Description
    ISO 4217 code. Defaults to NGN when amount is set.
  • occurred_at
    Required:
    No
    Description
    ISO 8601 time the event happened. Defaults to now and cannot be in the future. Reconciliation ranges use this time.
  • customer_id
    Required:
    No
    Description
    Your id for the customer, for your own matching.
  • customer_ip
    Required:
    No
    Description
    The customer's IP address, if you have it. We store a hash and use it in fraud checks. Without it, the request's own address is used.
  • refund_of
    Required:
    For refunds
    Description
    The event_id of the purchase being refunded.
  • metadata
    Required:
    No
    Description
    Up to 20 keys of your own. Values must be strings, numbers or booleans.
curl https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer op_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "type": "purchase",
    "event_id": "order_10023",
    "click_id": "01JBZ7Q4M2X8RC5T9VK3NHW6AE",
    "amount": 15000.50,
    "customer_id": "cust_9",
    "occurred_at": "2026-11-17T10:00:00Z",
    "metadata": { "plan": "family", "first_order": true }
  }'
Response 201 (new event)
{
  "duplicate": false,
  "event": {
    "id": "evt_01jcz8m5b6q7r8s9t0v1w2x3y4",
    "object": "event",
    "event_id": "order_10023",
    "type": "purchase",
    "mode": "live",
    "outcome": "converted",
    "reason": null,
    "offer_id": 42,
    "click_id": "01JBZ7Q4M2X8RC5T9VK3NHW6AE",
    "ref": "TOLU7X",
    "amount": 15000.5,
    "currency": "NGN",
    "customer_id": "cust_9",
    "refund_of": null,
    "conversion": {
      "id": 991,
      "status": "pending",
      "payout_amount": 800,
      "unit_cost": 960,
      "hold_until": "2026-11-24T10:00:00.000000Z",
      "paid_at": null,
      "rejection_reason": null,
      "simulated": false
    },
    "metadata": { "plan": "family", "first_order": true },
    "occurred_at": "2026-11-17T10:00:00.000000Z",
    "received_at": "2026-11-17T10:00:01.000000Z"
  }
}

Sending the same event_id again returns 200 with the first event, unchanged, and "duplicate": true. payout_amount is what the padi earns and unit_cost is what you pay (payout plus the platform fee), both in whole naira.

Outcomes

outcome says what the event did. Every outcome is a success: the event was understood and stored, so do not retry it. conversion.status is read fresh each time you fetch the event, so it moves from pending to approved (paid to the padi) or rejected.

  • converted
    reason:
    none
    Meaning
    A conversion was recorded. conversion.status is pending (paid when the hold ends) or approved (paid at once on an offer with a 0-day hold).
  • rejected
    reason:
    budget_exhausted, outside_window, offer_closed, link_blocked, fraud
    Meaning
    Attributed to a padi but not paid. Kept so you can see the demand you did not pay for.
  • duplicate
    reason:
    already_recorded
    Meaning
    This order was already recorded, for example by a postback with the same external_id. conversion is that earlier conversion.
  • logged
    reason:
    not_paid_event
    Meaning
    Attributed, but the offer pays for a different type. See paid event type.
  • unattributed
    reason:
    none
    Meaning
    No click_id or ref. A sale that did not come through a padi. Stored for reconciliation.
  • refunded
    reason:
    none
    Meaning
    A refund that reversed the purchase's pending conversion. Nothing is charged for it.
  • refund_after_payout
    reason:
    already_paid, hold_ended
    Meaning
    A refund for a conversion that had already paid, or whose hold had ended. Paid conversions are final. These show in reconciliation for support to review.
  • ignored
    reason:
    unknown_original, partial_refund, no_conversion, already_rejected
    Meaning
    A refund with nothing to reverse.

Why an attributed sale is rejected

  • offer_closed
    Meaning
    The offer is completed (filled, cancelled or expired) or was rejected at review. Paused offers still accept conversions.
  • link_blocked
    Meaning
    You blocked this padi's link.
  • outside_window
    Meaning
    The click is older than the offer's attribution window.
  • budget_exhausted
    Meaning
    Every slot on the offer is already paid or pending.
  • fraud
    Meaning
    Our fraud checks held it back, for example a conversion from the padi's own network or one that arrived seconds after the click.

POST /events, type refund

Refunds

Send a refund event with its own event_id and refund_of set to the purchase's event_id.

curl https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer op_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "type": "refund", "event_id": "refund_10023", "refund_of": "order_10023" }'
  • A full refund (no amount, or an amount at least the purchase's) reverses a pending conversion before it pays. The slot and its budget go back to the offer.
  • A partial refund leaves the conversion alone (ignored / partial_refund), because a sale still happened.
  • Once a conversion has paid, a refund cannot reverse it. You get refund_after_payout and the row shows in reconciliation.
  • Refunds also find conversions reported by the postback before you moved to the API, by matching refund_of against the postback's external_id.

POST /events/batch

Batch

Up to 100 events in one request, each handled on its own, so one bad event does not stop the rest. Use it for a nightly sync of every order. An empty list or more than 100 events is a 422 for the whole request. A batch counts as one request against the rate limit.

curl https://api.opinionpadi.com/api/v1/offers/events/batch \
  -H "Authorization: Bearer op_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "events": [
      { "type": "purchase", "event_id": "order_1", "click_id": "01JBZ7Q4M2X8RC5T9VK3NHW6AE", "amount": 9000 },
      { "type": "purchase", "event_id": "order_2", "amount": 4000 },
      { "type": "purchase", "event_id": "order_3", "ref": "NOPE22" }
    ]
  }'
Response 200
{
  "object": "batch",
  "received": 3,
  "succeeded": 2,
  "failed": 1,
  "results": [
    { "index": 0, "ok": true, "duplicate": false, "event": { "event_id": "order_1", "outcome": "converted", "...": "..." } },
    { "index": 1, "ok": true, "duplicate": false, "event": { "event_id": "order_2", "outcome": "unattributed", "...": "..." } },
    { "index": 2, "ok": false, "error": { "code": "unknown_ref", "message": "No padi link with this ref on your offers.", "param": "ref" } }
  ]
}

GET /events, GET /conversions

Events and conversions

GET /events/{event_id} returns one event with its conversion's current status. Encode the id for the URL. GET /events lists events newest first. Test keys list test events and live keys list live events.

GET /conversions lists every conversion on your offers, whatever reported it (api, postback or manual), so your system can match each one to an order. Test keys get an empty list, since they never create conversions.

# One event, with its conversion's current status
curl https://api.opinionpadi.com/api/v1/offers/events/order_10023 \
  -H "Authorization: Bearer op_sk_live_..."

# Events, newest first
curl "https://api.opinionpadi.com/api/v1/offers/events?offer_id=42&outcome=converted&from=2026-11-01&to=2026-11-17" \
  -H "Authorization: Bearer op_sk_live_..."

# Every conversion on your offers, whatever reported it
curl "https://api.opinionpadi.com/api/v1/offers/conversions?status=pending&per_page=100" \
  -H "Authorization: Bearer op_sk_live_..."
  • GET /events
    Filters:
    offer_id, type, outcome, from, to, page, per_page
    from / to apply to
    occurred_at
  • GET /conversions
    Filters:
    offer_id, status, source, external_id, from, to, page, per_page
    from / to apply to
    when it was recorded

from and to are Y-m-d days in Africa/Lagos time. per_page defaults to 50 with a maximum of 100. Without from and to the lists cover all time. Lists return data, page, per_page, total and has_more.

GET /reconciliation

Reconciliation

Lines up the events you sent against the conversions we recorded for a range of days. Filters: offer_id, from and to (Y-m-d in Africa/Lagos, default the last 30 days). Events are counted on occurred_at, conversions on when they were recorded.

curl "https://api.opinionpadi.com/api/v1/offers/reconciliation?offer_id=42&from=2026-11-01&to=2026-11-17" \
  -H "Authorization: Bearer op_sk_live_..."
  • sales: every non-refund event with an amount, per currency. attributed_* counts the ones that converted or matched a conversion already recorded.
  • conversions: what we recorded in the range and what it costs you. without_event counts pending and paid conversions that no event of yours points to.
  • discrepancies: four lists, each capped at 100 rows with has_more when there are more.

What each discrepancy means

conversion_without_event

We recorded a conversion that no event of yours points to. Usually a manual entry or a conversion reported by the older postback.

What to do: Check it against your orders while the hold is open. If it is a real sale, send its event. If it is not, reject the conversion in the dashboard before the hold ends.

event_conversion_rejected

You sent a sale that converted, and the conversion was later rejected: by you in the dashboard, by support, or by a refund.

What to do: Nothing is charged for it. No action needed unless you think the rejection was a mistake.

rejected_event

A sale attributed to a padi that was not paid. The row carries the reason.

What to do: Read the reason. budget_exhausted means the offer had no slots left when the sale came in. outside_window means the click was older than the offer's attribution window, and offer_closed means the offer had ended. Talk to support about a fraud rejection you disagree with.

refund_after_payout

A refund for a conversion that had already paid.

What to do: Paid conversions are final and the API cannot reverse them. Support reviews these rows.

With a test key the report covers test events, and conversions is built from their simulated results.

Response 200
{
  "object": "reconciliation",
  "mode": "live",
  "offer_id": null,
  "range": { "from": "2026-10-19", "to": "2026-11-17", "timezone": "Africa/Lagos" },
  "events": {
    "total": 2,
    "by_outcome": { "converted": 1, "duplicate": 0, "rejected": 0, "logged": 0, "unattributed": 1, "refunded": 0, "refund_after_payout": 0, "ignored": 0 },
    "by_type": { "purchase": 2 }
  },
  "sales": [
    { "currency": "NGN", "events": 2, "amount": 14000, "attributed_events": 1, "attributed_amount": 10000 }
  ],
  "conversions": {
    "pending": 2, "paid": 0, "rejected": 0,
    "pending_cost": 1920, "paid_cost": 0,
    "with_event": 1, "without_event": 1,
    "currency": "NGN"
  },
  "discrepancies": {
    "conversion_without_event": {
      "rows": [
        {
          "conversion_id": 992, "offer_id": 42, "ref": "TOLU7X", "source": "manual",
          "external_id": "manual_1", "status": "pending", "unit_cost": 960,
          "hold_until": "2026-11-24T10:00:00.000000Z", "recorded_at": "2026-11-17T11:00:00.000000Z",
          "action": "Check this against your orders. If it is a real sale, send its event; if not, reject it before the hold ends."
        }
      ],
      "has_more": false
    },
    "event_conversion_rejected": { "rows": [], "has_more": false },
    "rejected_event": { "rows": [], "has_more": false },
    "refund_after_payout": { "rows": [], "has_more": false }
  }
}

GET /balance

Balance

Your wallet and what is left on each offer's budget, so your system can warn you before an offer runs out. Without offer_id it lists offers that are live, awaiting review, or closed with conversions still in their hold. It only reads, so test keys see the real figures. Amounts are whole naira.

curl https://api.opinionpadi.com/api/v1/offers/balance \
  -H "Authorization: Bearer op_sk_live_..."

# One offer, including a closed one
curl "https://api.opinionpadi.com/api/v1/offers/balance?offer_id=42" \
  -H "Authorization: Bearer op_sk_live_..."
Response 200
{
  "object": "balance",
  "currency": "NGN",
  "wallet": { "available": 250000, "pending": 0 },
  "offers": {
    "budget_remaining": 48000,
    "reserved": 960,
    "unreserved": 47040,
    "remaining_slots": 49
  },
  "by_offer": [
    {
      "offer_id": 42,
      "title": "First order on Mama Put",
      "status": "approved",
      "unit_cost": 960,
      "quantity": 50,
      "paid_count": 0,
      "pending_count": 1,
      "remaining_slots": 49,
      "budget_total": 48000,
      "budget_remaining": 48000,
      "reserved": 960,
      "unreserved": 47040,
      "accepts_conversions": true
    }
  ]
}
  • wallet.available
    Meaning
    Money in your wallet that is not on any offer. Top up an offer from it in the dashboard.
  • budget_remaining
    Meaning
    What is left of an offer's budget.
  • reserved
    Meaning
    Held for conversions still in their hold: pending_count × unit_cost.
  • unreserved
    Meaning
    Pays for new conversions, and comes back to the wallet if the offer closes.
  • remaining_slots
    Meaning
    Conversions the offer can still take. At 0, new sales are stored as rejected / budget_exhausted.
  • accepts_conversions
    Meaning
    The offer is live and has room for at least one more conversion.

Test mode

A test key (op_sk_test_) runs every event through the same validation and attribution as live, then stops. Nothing is recorded against an offer, no budget is reserved and no padi is paid. conversion holds what would have happened, with "simulated": true and "id": null.

Against a real offer

Open one of your offer's padi links yourself, or take a real click_id from your logs, and send the event with a test key. The simulation applies the offer's real state: closed offers, blocked links, the attribution window and the budget. Fraud checks are skipped, since they depend on real padi activity. The first test event that reaches a real offer marks the offer's integration as verified.

With test values

Put one of these in click_id or ref to play a fixed scenario with no click needed. Add offer_id to get that offer's payout and unit cost in the simulated conversion. Refunds play out against the test purchase they point to. Test values sent with a live key are refused with test_value_in_live_mode.

  • op_test_converted
    Result
    converted, conversion pending
  • op_test_converted_paid
    Result
    converted, conversion approved. A refund of it gives refund_after_payout.
  • op_test_budget_exhausted
    Result
    rejected / budget_exhausted
  • op_test_outside_window
    Result
    rejected / outside_window
  • op_test_offer_closed
    Result
    rejected / offer_closed
  • op_test_link_blocked
    Result
    rejected / link_blocked
  • op_test_fraud
    Result
    rejected / fraud
  • op_test_unknown
    Result
    422 unknown_click (or unknown_ref when sent as ref)

Copy-paste test events

# A purchase that converts
curl https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer op_sk_test_..." -H "Content-Type: application/json" \
  -d '{"type":"purchase","event_id":"test_order_1","click_id":"op_test_converted","offer_id":42,"amount":15000}'

# Its refund
curl https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer op_sk_test_..." -H "Content-Type: application/json" \
  -d '{"type":"refund","event_id":"test_refund_1","refund_of":"test_order_1"}'

# A sale after the budget ran out
curl https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer op_sk_test_..." -H "Content-Type: application/json" \
  -d '{"type":"purchase","event_id":"test_order_2","ref":"op_test_budget_exhausted"}'

The Developers page in the business dashboard can send the same test events without a key, and shows the test event log.

Errors and retries

Anything we could not act on returns a 4xx with one error object. Nothing is stored for an event that fails, so fix it and retry with the same event_id.

Response 422
{
  "error": {
    "code": "unknown_click",
    "message": "No click with this click_id on your offers. Send the op_click value from the landing URL exactly as received.",
    "param": "click_id"
  }
}
  • 401
    code:
    missing_api_key, invalid_api_key, api_key_revoked
    Meaning
    Check the Authorization header and that the key has not been revoked.
  • 404
    code:
    event_not_found, unknown_offer
    Meaning
    Nothing with that id on your account.
  • 409
    code:
    conflict
    Meaning
    The same event_id is being processed by another request. Retry.
  • 422
    code:
    invalid_request
    Meaning
    A field is missing or malformed. param names it.
  • 422
    code:
    unknown_click
    Meaning
    No click with this click_id on your offers.
  • 422
    code:
    unknown_ref
    Meaning
    No padi link with this ref on your offers.
  • 422
    code:
    offer_mismatch
    Meaning
    The click or ref belongs to a different offer than offer_id.
  • 422
    code:
    test_value_in_live_mode
    Meaning
    An op_test_ value was sent with a live key.
  • 422
    code:
    unknown_test_value
    Meaning
    An op_test_ value that is not one of the test scenarios.
  • 429
    code:
    none
    Meaning
    Too many requests. Wait for the number of seconds in Retry-After.

Retries

  • Retry 409, 429, 5xx and network errors with backoff. On 429, wait for the seconds in Retry-After.
  • Retrying is always safe because event_id makes events idempotent. A retry of an event that did get through returns the first result with "duplicate": true.
  • Do not retry other 4xx unchanged. Fix the field named in param first.
  • The SDKs retry for you, up to max_retries times (default 2), and raise one error type with status, the error code, param and the message.
# Non-2xx responses carry one error object. Retry 409, 429 and 5xx with
# backoff, always with the same event_id. Do not retry other 4xx unchanged.
curl -sS -w "\nHTTP %{http_code}\n" https://api.opinionpadi.com/api/v1/offers/events \
  -H "Authorization: Bearer op_sk_test_..." -H "Content-Type: application/json" \
  -d '{"type":"purchase","event_id":"test_order_9","click_id":"op_test_unknown"}'

The older postback

Before the events API, each offer had its own postback token: your server called /api/v1/offers/postback with the token, the stored click_id or ref and your external_id. It keeps working, and you can find the token and exact URL on the offer's integration screen in the dashboard.

The two never count the same order twice: an event's event_id and a postback's external_id are the same key. For new integrations use the events API. It adds refunds, unattributed sales, batches, simulated test events and reconciliation.

Postback
# Form body
curl -X POST "https://api.opinionpadi.com/api/v1/offers/postback" \
  -d token=YOUR_OFFER_POSTBACK_TOKEN \
  -d click_id=01JBZ7Q4M2X8RC5T9VK3NHW6AE \
  -d external_id=ORDER_123 \
  -d amount=25000

# Check the integration (records nothing)
curl "https://api.opinionpadi.com/api/v1/offers/postback?token=YOUR_OFFER_POSTBACK_TOKEN&test=1"
  • token
    Notes
    The offer's postback token, or the X-OpinionPadi-Token header.
  • click_id
    Notes
    The op_click value. Preferred. One of click_id or ref is required.
  • ref
    Notes
    The padi's code, used only when click_id is absent.
  • external_id
    Notes
    Your id for the conversion. Required with ref, recommended always.
  • amount
    Notes
    Order value in whole naira, for reports.
  • test
    Notes
    1 checks the token and marks the postback verified. Creates no conversion.

Get a test key

Sign in to the business dashboard, open the Developers page and create a test key. Send the test events above, then switch to a live key when your offer is approved.

We value your privacy

We use essential cookies to keep OpinionPadi secure. With your permission, we'll also use cookies to remember your preferences and improve advertising relevance through Google AdSense and other partners. You can manage your choices at any time.

Read more in our Privacy Policy.