Send files from your code.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "final-cut.mp4", "size": 734003200 }],
    "recipients": ["client@example.com"],
    "message": "The final cut — enjoy."
  }'

{
  "id": "d23583b7-05f1-4d7f-a6bd-a1e28af4e3b1",
  "status": "draft",
  "mode": "test",
  "shortCode": "SSyNuWN",
  "uploads": [{
    "fileId": "a512b334-…",
    "mode": "multipart",          // or "single" under 100 MB, with a ready url
    "uploadId": "…", "partSize": 16777216, "partCount": 44
  }],
  "manageToken": "b_mKzpcj…"      // shown once — X-Transfer-Token from here on
}

Give each file a name and its exact size in bytes — the size picks the upload shape (one PUT under 100 MB, multipart above) and is checked against your plan, then reconciled against the real bytes when you finalize. On a test key you can omit recipients entirely: every test delivery goes to your own account email.

# single mode (files under 100 MB): one PUT
curl -X PUT "<uploads[0].url>" \
  -H "x-amz-content-sha256: UNSIGNED-PAYLOAD" \
  --data-binary @final-cut.mp4

# multipart (larger): fetch part URLs in batches, PUT each part,
# then complete with the ETags
curl -X POST https://api.ivesentit.com/v1/transfers/<id>/files/<fileId>/parts \
  -H "X-Transfer-Token: <manageToken>" \
  -d '{ "partNumbers": [1, 2, 3] }'

Every upload URL is signed, single-purpose and expiring — and lives on our domain, never a raw cloud hostname.

curl -X POST https://api.ivesentit.com/v1/transfers/<id>/finalize \
  -H "X-Transfer-Token: <manageToken>"

Scanning starts. The delivery email goes out when everything is clean and packaged — with a signed delivery certificate your recipient can verify.

curl https://api.ivesentit.com/v1/deliveries/<id> \
  -H "Authorization: Bearer ivst_live_..."

curl "https://api.ivesentit.com/v1/events?after=<last-id>" \
  -H "Authorization: Bearer ivst_live_..."

{
  "id": "d23583b7-…", "status": "ready", "testMode": true,
  "certificateId": "DLV-D23583B7-TLPJLB",   // every delivery carries signed proof
  "files": [{ "name": "final-cut.mp4", "uploaded": true, "scan": "clean" }],
  "recipients": [{ "to": "client@example.com", "opens": 2, "downloads": 1 }]
}

{ "events": [
  { "type": "delivery.created",  "data": { "transferId": "d23583b7-…" } },
  { "type": "delivery.sent",     "data": { "certificateId": "DLV-…" } },
  { "type": "delivery.opened",   "data": { "recipient": "client@…", "country": "GB" } },
  { "type": "delivery.downloaded", "data": { "bytes": 734003200 } }
], "nextAfter": null }

Status shows per-file scan state and per-recipient opens and downloads. Events are cursor-paged, oldest first, kept 30 days.

Recipients must enter the password before anything opens. Share it through a different channel than the delivery email.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "accounts-2026.xlsx", "size": 48210 }],
    "recipients": ["fd@client.com"],
    "password": "correct-horse-battery"
  }'

The password is never stored in plain text and never appears in any email.

Name the countries the delivery may be collected from — it refuses everywhere else, at the edge.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "master-audio.wav", "size": 812349440 }],
    "recipients": ["label@partner.co.uk"],
    "allowedCountries": ["GB", "IE"]
  }'

Two-letter ISO codes. Attempts from outside the wall are refused before any bytes move.

Set the total number of downloads the delivery allows before it seals itself.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "press-kit.pdf", "size": 9210331 }],
    "recipients": ["press@outlet.com"],
    "downloadCap": 3
  }'

The cap counts completed downloads across all recipients. It cannot be combined with viewOnce (they contradict — the API tells you so).

The delivery burns after its first collection — one look, then gone.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "credentials.pdf", "size": 102400 }],
    "recipients": ["new-hire@company.com"],
    "viewOnce": true
  }'

After the first successful collection the delivery is sealed for everyone, sender included.

The delivery email goes out now; the files stay sealed until the embargo lifts.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "earnings-q3.pdf", "size": 421889 }],
    "recipients": ["press@wire.com"],
    "releaseAtTime": 1790244000
  }'

Unix seconds. Recipients see a countdown, not the files, until the moment arrives.

Every recipient gets their own marked copy — a leaked screener points back to exactly one person.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "episode-1-screener.mp4", "size": 2147483648 }],
    "recipients": ["critic-a@outlet.com", "critic-b@paper.co"],
    "watermark": true,
    "watermarkLabel": "CONFIDENTIAL SCREENER"
  }'

Needs at least one named recipient (the mark is per person). watermarkLabel is optional extra text alongside the recipient identity.

The files stay locked until the recipient passes an identity check. Add confirm mode and you release each verified person by hand.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "settlement-agreement.pdf", "size": 220144 }],
    "recipients": ["counterparty@firm.law"],
    "idVerify": true,
    "idVerifyConfirm": true
  }'

Needs named recipients. With idVerifyConfirm the sender reviews each verification and releases the files per person; without it, passing the check unlocks automatically.

Attach a price. Your client pays by card, the files unlock, and the money lands in your own Stripe account — we take 0%.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "wedding-highlights.mp4", "size": 5368709120 }],
    "recipients": ["couple@example.com"],
    "priceCents": 45000,
    "priceCurrency": "gbp"
  }'

Needs Stripe payouts set up on your account first (Account → Get paid), and at least one named recipient — each personal link is one purchase.

Two small switches: linkOnly makes a send with no recipients (you share the link yourself); notifyOnOpen emails you on first open.

curl -X POST https://api.ivesentit.com/v1/deliveries \
  -H "Authorization: Bearer ivst_live_..." -H "Content-Type: application/json" \
  -d '{
    "files": [{ "name": "portfolio.pdf", "size": 18320441 }],
    "linkOnly": true,
    "notifyOnOpen": true
  }'

A recipient-less send must say linkOnly: true explicitly — silently losing recipients should never look like success.