Activity

Activity is the record of what this vendor has actually sent you — every posted lead, newest first, with the answer it got back. It’s read-only, and it’s where you go when a partner says they’ve been sending leads and you can’t find them.

Every vendor has this tab. It shows the last 100 posts; Refresh re-reads it.

Recent posts

Column	What it means
When	When the post arrived, in your local time
Result	The code and outcome — see below
Phone	The last 4 digits only. Full numbers are never kept in this log
Email	The email they sent, if any
Ref	The partner’s own reference for that lead, if they sent one

A reference in Ref is also a safety net: if the partner re-sends a lead with a reference already in this log, they get the original answer back instead of creating a second contact, so a retry after a timeout can’t double-post.

Result is colour-coded three ways: green for accepted, amber for rejected, red for an error. That’s the distinction that matters.

• Accepted — the lead is in. You’ll find the contact in this vendor’s list.
• Rejected — it arrived fine and your rules turned it down. Working as configured; nothing to fix unless the volume surprises you.
• Error — the post never got as far as your rules. Something is wrong with the setup, and it’s usually yours to fix.

Code	Outcome	Meaning
100	accepted	New lead created
101	accepted	Existing contact updated
102	accepted	Duplicate accepted, existing contact left unchanged
200	rejected	No valid phone number provided
201	rejected	Phone number failed validation
202	rejected	Outside the calling area — US and toll-free numbers only
210	rejected	Duplicate lead
220	rejected	Number is on the do-not-call list
403	error	Posting is disabled for this vendor
500	error	Server error — safe to retry

Which of 101, 102 and 210 a duplicate gets is your On duplicate choice on General.

Reading a failed post

A run of 403s means the vendor is switched off. Its Status is Deactivated, or it’s archived. The partner is still trying; you’re refusing. Turn it back on, or tell them to stop.

A run of 202s means they’re selling you leads outside the area you can call. That’s a conversation with the partner, not a setting to change.

200s and 201s are their data quality — the phone field is missing or unusable. Send them the printable instructions from Post API; it states exactly what a phone number has to look like.

Lots of 220s means you’re being sent numbers already on your do-not-call list. Those rejections are never optional and never configurable.

A wrong key shows up here as nothing at all

A post sent with an invalid key, or to the wrong vendor’s address, is refused before it’s recorded — so it never appears on this screen. The partner sees the refusal in their own system; you see an empty log. If someone insists they’re sending leads and this tab shows nothing, assume the key first: re-send them the link from Post API. This is also exactly what regenerating a key looks like from your side.

An empty log doesn’t always mean they never posted

Posts are kept for 90 days and then dropped, and only the most recent 100 are shown here. A partner asking about a lead from last quarter cannot be answered from this screen. If a post’s outcome matters for a payment dispute, capture it while it’s here.

Your partner can read a version of this themselves, without you, on the results log linked from Post API — the same posts and the same codes, minus the email address, and each line opens to show the location, reference and source that arrived with the lead.