Docs

Report sent messages

messages.report_send tells Amdahl which optimize runs went out, where and to whom, so a run can be matched to what was sent. Up to 100 sends a call. The recipient and the sent text are stored as SHA-256 hashes only.

Report each send from your agent or sequencer, and Amdahl knows which optimized messages went out, where, and whether someone edited them first. messages.report_send tells Amdahl that messages from optimize runs went out. Your sequencer, inbox integration or agent sends one item per message sent: the run_id the optimize returned, where it went out, when, and whether it went out as returned or edited. Amdahl stores the report against the run, so each run can be matched to what was actually sent.

OperationRESTMCPScope
Report sent messagesmessages.report_sendPOST /messages/report_sendreport_message_sentmessages:execute

It needs the editor role or above. It does not count toward the monthly cap. Calls count against the standard rate limit.

What to send

Send items, a list of 1 to 100 sends. Each item:

FieldRequiredMeaning
run_idyesThe run_id the optimize returned for this message. Upper or lower case.
provideryesWhere it went out: lemlist, instantly, outreach, salesloft, hubspot, salesforce, gmail, heyreach, apollo, smartlead, reply_io, lgm, woodpecker, linkedin_manual or other.
channelyesemail, linkedin_invite, linkedin_message or linkedin_inmail.
sent_asyesreturned (sent as Amdahl returned it) or edited (changed before sending).
sent_atyesWhen it was sent: an ISO 8601 timestamp with a time zone, such as 2026-10-27T15:04:00Z.
provider_send_idsee belowThe provider's own id for this send. Which id to send depends on the provider: see Which id to send.
recipientsee below, and send it with every reportThe email address (for email) or LinkedIn profile URL (for the LinkedIn channels) it went to. Amdahl hashes it and stores only the hash.
recipient_key_hashsee belowInstead of recipient: your own hash of it, made as described in Hashes.
sent_textnoThe text as sent. Amdahl hashes it and stores only the hash. Useful with sent_as: "edited".
provider_campaign_idnoThe provider's campaign or sequence id.
sequence_stepnoThe provider's own step index, 0 to 1000. Lemlist's first step is 0.
provider_variant_idnoThe provider's id for the variant sent, for A/B tests.
provider_lead_idnoThe provider's id for the recipient, such as Lemlist's lea_... id.
thread_idnoThe email thread or LinkedIn conversation id.

Each item needs provider_send_id, or a recipient (recipient or recipient_key_hash), or both. Send recipient or recipient_key_hash, not both. Send the recipient with every report, even one that has a provider_send_id: it lets a report with an id and one without count as one send, and it is what you can match on later.

Which id to send

provider_send_id is the id the provider gives the send, in the form Amdahl matches to outcomes:

ProviderSend this as provider_send_id
lemlistThe _id of the emailsSent, linkedinSent or linkedinInviteDone activity (act_...). Not the lead id or the message id.
hubspotThe hs_object_id of the email engagement: digits only.
gmailThe Message-ID header with its angle brackets, such as <[email protected]>. Not the Gmail API message id. A gmail value without angle brackets is rejected with invalid_provider_id, because an address and a bare Message-ID look alike.
instantly, outreach, salesloft, salesforce, heyreach, apollo, smartlead, reply_io, lgm, woodpecker, linkedin_manual, otherThe provider's own id for the send. It is stored, and Amdahl does not match these to outcomes yet.

A Lemlist send with no activity id can be sent with provider_campaign_id, provider_lead_id and sequence_step (the provider's own index, starting at 0) and a recipient. Amdahl finds the send from those.

bash
curl -s -X POST https://app.amdahl.ai/api/platform/v1/messages/report_send \
  -H "X-API-Key: $AMDAHL_KEY" -H "Content-Type: application/json" \
  -d '{
    "items": [
      {
        "run_id": "0b6a6c1e-4f5d-4c1a-9d1e-2f3a4b5c6d7e",
        "provider": "lemlist",
        "channel": "email",
        "provider_send_id": "act_8f2c1d",
        "provider_campaign_id": "cam_q4_ops",
        "sequence_step": 0,
        "recipient": "[email protected]",
        "sent_as": "edited",
        "sent_text": "Hi Priya, ...",
        "sent_at": "2026-10-27T15:04:00Z"
      }
    ]
  }'

What comes back

One result per item, in the order sent:

json
{
  "success": true,
  "accepted": 1,
  "rejected": 1,
  "items": [
    { "index": 0, "run_id": "0b6a6c1e-...", "status": "accepted", "result": "created" },
    { "index": 1, "run_id": "5d2e9f40-...", "status": "rejected", "reason": "run_not_found", "message": "No optimize run with this run_id in this workspace." }
  ]
}

An accepted item is created, or updated when an earlier report of the same send was stored. A rejected item is not stored, and the other items in the call still are. The reasons:

reasonWhy
run_not_foundNo run with this run_id in this workspace. A run from another workspace and an id that does not exist get the same answer.
invalid_recipientrecipient is not an email address for the email channel or a LinkedIn profile URL for a LinkedIn channel, recipient_key_hash is not 64 hexadecimal characters, or both were sent.
missing_send_keyThe item has no provider_send_id and no recipient.
sent_at_in_futuresent_at is more than 10 minutes ahead of the server clock.
sent_at_too_oldsent_at is before 2000-01-01.
sent_at_before_runsent_at is more than 5 minutes earlier than the optimize run that wrote the message. A send cannot come before its run.
invalid_provider_idprovider_send_id, provider_lead_id, provider_campaign_id, provider_variant_id or thread_id holds an email address or a LinkedIn profile URL. Send the provider's own id. These fields are stored as sent, so a personal identifier in one is refused. The check looks at the whole value: an email Message-ID in angle brackets, such as <[email protected]>, is accepted.
run_send_limitThe run already holds 500 stored sends. A repeat of a stored send is still accepted.
daily_send_limitThe workspace has stored or updated 50,000 reports in the last 24 hours. A repeat of a stored send is still accepted.

A call whose shape is wrong (a missing required field, an unknown value, an unknown field, a NUL character or a lone surrogate in a text field, more than 100 items) is refused as a whole with 400, and nothing is stored. A key without messages:execute gets 403 forbidden.

Repeats and retries

A report is one send, so a retry or a second report of the same send updates the stored row and adds no new one:

  • With provider_send_id, one send is the run, the provider and the provider_send_id.
  • Without it, one send is the run, the recipient and sent_at. A different sent_at is a different send.

A report with a provider_send_id also matches a stored report of the same send that had none: one with the same run, recipient and sent_at. It adds the id to that row. A report without an id updates a stored report of the same recipient and sent_at that has one. So the same send reported both ways is still one row.

A later report replaces sent_as and channel (and sent_at, when the send is keyed by provider_send_id), and fills the optional fields it sends. A field it leaves out keeps its stored value.

Hashes

Amdahl never stores the recipient's address or the sent text. It stores a SHA-256 hash of each, as lowercase hexadecimal:

  • Email address: remove spaces at both ends, change to lowercase, then hash. " [email protected] " and "[email protected]" give the same hash.
  • LinkedIn profile URL: Amdahl uses the canonical form https://www.linkedin.com/in/<profile>, with the profile name lowercase and with no query string or trailing slash, then hashes it. linkedin.com/in/Priya-S/ and https://www.linkedin.com/in/priya-s give the same hash. A profile name with non-ASCII characters is percent-encoded as UTF-8 first: linkedin.com/in/josé is hashed as https://www.linkedin.com/in/jos%C3%A9.
  • Sent text: change \r\n and \r line endings to \n, remove spaces and line breaks at both ends, then hash.

To send recipient_key_hash yourself, hash the same normalized form.

From an agent

An agent connected over MCP calls report_message_sent with the same items. An agent run inside Amdahl, such as a research job, cannot report sends: it does not see what was sent outside it.