Publisher portal

After this page you can switch a publisher's portal on, invite the right people to it, choose what each of them may read, and answer confidently when a partner asks what the portal shows them about your buyers. The short answer is nothing.

The publisher portal answers the questions a partner would otherwise send to you — "did my call come through?", "why did you not bid?", "what am I owed?" — from the same records you read, cut down to their own side. It is available on plans that include it; see pricing.

Switching it on

1. 1

   Turn the portal on for that publisher

   It is off until you do. An invitation to a door that will not open is worse than no invitation, so inviting anybody before this is refused with a sentence saying so.

2. 2

   Invite a person

   An invitation is per email address and lasts seven days. The token comes back once and is what the invitee exchanges for a login.

   curlCopy

   curl -X POST "https://api.buy3.io/api/publishers/c4e1a2b3-9d8f-4f6e-b5a4-1c2d3e4f5a6b/invitations" \
     -H "Authorization: Bearer $BUY3_SESSION_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{ "email": "ops@example.com", "invitedName": "Northwind operations" }'

   201Copy

   {
     "invitation": {
       "id": "8e7d6c5b-4a39-4827-9615-04938271650a",
       "email": "ops@example.com",
       "expiresAt": "2026-09-27T10:14:02.000Z"
     },
     "token": "5b4a39281706495883726150493827160ab1cd2e",
     "note": "Store this token now — it is shown only once."
   }

3. 3

   Set what they may read

   Each member carries a role and three independent switches. They are switches rather than roles because the questions they answer are genuinely independent — the person who chases missing calls is often not the person who should see money.

What a publisher sees

{
  "id": "3f2e1d0c-9b8a-4765-8432-10fedcba9876",
  "ref": "AU-100483",
  "at": "2026-09-20T14:03:11.000Z",
  "campaign": { "id": "6a2d1f0e-8b7c-4c55-a1d3-0e9f8a7b6c5d", "name": "Acme Health inbound" },
  "outcome": "no_bid",
  "reason": {
    "code": 1006,
    "reason": "outside_hours",
    "sentence": "The ping arrived outside the hours this campaign, or your lane on it, is open.",
    "owner": "network"
  },
  "payoutCents": 0,
  "elapsedMs": 41,
  "callerMasked": "••••••0142",
  "callerState": "TX",
  "environment": "production",
  "publisherRef": "lead-88231",
  "externalCallId": "pbx-5531902",
  "statusCode": 200,
  "expiresAt": null,
  "callRef": null
}

Every refusal in their ledger carries an owner — whose move it is — and the summary adds them up. It is the one line that tells a publisher whether to look at their own integration or pick up the phone.

What a publisher never sees

• A buyer price, a bid, or a margin. Not directly, and not as two numbers that divide into one — which is why a revenue-share lane reports its mode, its floor and its ceiling and never the percentage.
• Any buyer or target, by name or by id, on a call, a ping or a waterfall.
• Another publisher's anything, and no campaign they do not hold an active lane on.
• The caller's full number, unless the campaign discloses caller ID. Otherwise it is masked to the last four digits — in the column and inside the stored request, because a mask on one and not the other is decoration.
• Your internal notes about them, and the internal half of any change: an internal note is recorded in their activity as having changed, and no more.

Key health

A routing key that silently stopped working looks exactly like a campaign that went quiet, so the portal does not leave a publisher to work it out from a table. Routing keys carries a count of problems, and the overview flags them.

Rotating a key from the portal

A publisher can replace their own routing key only when both switches are on: the person holds Can rotate keys, and the key itself allows self-rotation. The first is their account owner deciding who may; the second is you deciding which lanes are safe to let a partner cut over unsupervised.

• The replacement keeps the lane's configuration — protocol, allowlist, rate limits, the single-step URL — so a rotation never quietly moves them onto a surface their key cannot use.
• The previous key keeps working for 24 hours, so they can deploy without dropping pings.
• A key that signs gets a fresh signing secret with its fresh key, and the two must be deployed together: the old key keeps the old secret for its grace window, and the new key only ever accepts the new one.
• Every rotation is on your activity log and on theirs, naming who did it.

Terms

A publisher account can carry a terms document and a version. When a version is published and nothing has been accepted, the portal shows it as outstanding until somebody accepts it, and records who accepted which version and when. Accepting twice does not move that record: the first acceptance is the one that happened.

A worked example

Northwind Media email on a Monday: "we sent 400 calls on Friday and only 90 came through — what is wrong with your endpoint?"

1. You switch their portal on and invite their operations address. They accept and land on Overview.
2. They open Ping log, set the window to Friday and sort by reason. Two thirds of the no-bids are 1008 state_not_targeted, owner publisher.
3. They open one of those pings. What the publisher sent shows state: "AR"; What we answered shows the refusal. Nothing about your buyers appears anywhere on the page.
4. They filter their own media to the three states on the lane. Their fill rate on Stats moves the same afternoon.
5. The remaining refusals are 1006 outside_hours, owner network. That one is yours: the lane's hours are narrower than they remember agreeing, and the change is on their Activity page with the old value and the new.

No call detail, no buyer name and no price left your side, and the conversation finished without either party guessing.

Next steps