Multi-file envelopes (POST /transfers)

POST /transfers builds bundle metadata; recipients open a gated public link (password and email OTP). Owner APIs expose list, revoke, and access logs under transfers:read / transfers:write.

Ship diligence packs and board decks as one gated envelope.

Mirror secure-sharing primitives: passwords, email allowlists, OTP, access logs — with POST /transfers creating a multi-file bundle and a gated public recipient flow (parallel to single-file /s/ links).

Value

One token, many files

POST /transfers accepts multiple tx-backed items and returns a stable public URL for recipients.

Same assurance primitives

Password prompts, OTP request/verify endpoints, and session parameters behave like encrypted share links.

Owner observability

List, fetch metadata, read access logs, and revoke bundles with transfers scopes — no guesswork.

For operators

• Start with POST /transfers including items[], optional password, allowedEmails, and expiry window.
• Recipients hit GET /transfers/access/:token; gated flows call request-code + verify-code exactly like shares.
• Use GET /transfers/:id/access-log for forensic review before you revoke with POST /transfers/:id/revoke.

For buyers

• Ideal for M&A rooms that need multiple attestations in one envelope without zipping plaintext.
• Gives compliance teams a second regulated channel distinct from single-file shares.
• Pairs naturally with Library selection UX in Evercore Console.