​

Walkthrough: bulk feedback import

​

1. When feedback matters

​

2. The shape of one record

​

3. The bulk import wizard

id,outcome
msg_0123456789abcdef0123456789abcdef,confirmed
msg_fedcba9876543210fedcba9876543210,unconfirmed
msg_aabbccddeeff00112233445566778899,confirmed

• A header row is detected and skipped when its first cell is id, sid, message_id, or messagesid — so a Twilio-shaped Sid,Outcome export and a Devotel id,outcome export both import without manual stripping.
• Outcome values are case-insensitive (Confirmed, CONFIRMED are accepted and lower-cased).
• Ids must match msg_<32 hex>; legacy or wrong-shaped ids are listed as per-line errors with the line number, never guessed.
• Duplicate ids are collapsed — first row wins — and the dialog reports how many duplicates it dropped.
• A batch accepts up to 1,000 valid rows. Rows beyond the cap are dropped with a truncation warning; split larger exports into batches.

​

4. Idempotency and retry semantics

• Re-posting the same outcome for a message is a no-op — the stamped timestamp is not rewritten.
• Flipping the outcome (e.g. unconfirmed → confirmed) refreshes the stamped timestamp, so the audit trail reflects the correction.
• Feedback writes touch only your own tenant’s message rows. There is no billing effect and no delivery side-effect.

​

5. Reading the result

{
  "data": {
    "updated": [
      { "id": "msg_0123456789abcdef0123456789abcdef", "outcome": "confirmed", "feedback_at": "2026-10-02T12:00:00.000Z" }
    ],
    "not_found": ["msg_fedcba9876543210fedcba9876543210"],
    "summary": { "requested": 2, "updated": 1, "not_found": 1 }
  }
}

• updated[] — rows the write touched, with the stamped outcome and timestamp.
• not_found[] — ids that matched no message in your account (retention purge, wrong tenant, or stale export). In the dashboard these render as an explicit list under Ids not found in this account. A not_found row is not worth retrying — reconcile the export upstream instead.

• Message detail — open a message in Messages and the stamped outcome appears alongside its delivery timeline.
• Insights goals and attribution — the feedback signal joins campaign, template, and channel lineage, so per-campaign and per-template conversion reads can reconcile against the imported outcomes. For paid campaigns, the Campaign ROAS and revenue attribution guide shows how the credited-revenue side reads; imported outcomes give it a conversion-side signal.

​

6. The API path

curl -X POST "https://api.orbit.devotel.io/api/v1/messages/feedback/bulk" \
  -H "X-API-Key: dv_live_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "items": [
      { "id": "msg_0123456789abcdef0123456789abcdef", "outcome": "confirmed" },
      { "id": "msg_aabbccddeeff00112233445566778899", "outcome": "unconfirmed" }
    ]
  }'

​

7. Role access