Send Subscription Docs
POST/v1/fundraisings/:id/send-subscription-docs
Stages a prospect on the Fund Admin closing linked to this fundraising and invites it, so Fund Admin emails the collaborators. Responds 202 as soon as the prospect exists — the invite runs after the response and its outcome is NOT reported here, so invitedEmails names who is being invited rather than who was reached. Poll Fund Admin (ContactState Prospect -> Invited) to confirm delivery. A send is recorded optimistically, so an immediate re-send is refused with ALREADY_SENT; if the invite fails that record is rolled back and a re-send is accepted, reusing the staged prospect rather than duplicating it. Concurrent sends are not serialised and can email the collaborators twice. Requires the organization to have the Carta integration enabled. Failures other than 403 carry a machine-readable code alongside message. Note PROSPECT_PERSIST_FAILED must never be retried — a retry stages a duplicate prospect on a live closing — and FA_REJECTED_REQUEST cannot succeed on identical input.
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 409
- 422
- 500
- 502
Prospect staged and the invite dispatched
Invalid request parameters
Invalid or missing API key
Read-only API key, Carta integration disabled, or Fund Admin permission denied
Fundraising not found
Subscription docs were already sent for this fundraising (code: ALREADY_SENT)
Fund not mapped, Carta identity missing, closings not set up, or Fund Admin refused the request
Internal server error, or the prospect was created in Fund Admin but not recorded in CRM (code: PROSPECT_PERSIST_FAILED — do not retry)
Fund Admin unreachable