Connect — onboard a Client and place an Investment
A 6-step recipe with Fundrise. We can help you get access.
Recipe · 6 steps
Connect — onboard a Client and place an Investment
with Fundrise · Customer Onboarding Management
Onboard an end user as a Fundrise Client and place their first investment.
- Onboard the end user. Partner HTTP Basic auth. A 409 means this partnerReferenceId already maps to an existing Client — treat that as a successful no-op and resolve the existing Client rather than retrying with a new key.
- Exchange the refresh token issued at Client creation for a Client-scoped access token. The refresh token does not expire and must be stored encrypted at rest — never expose it to the Client or a Client device.
- List offerings available through Connect. Select one whose status is OPEN — CLOSED offerings cannot be invested in. Partner HTTP Basic auth.
- Fetch the documents and disclosures for the selected offering. These must be presented to the Client. Collect every documentId — they are required as acknowledgedDocumentIds on the investment request.
- Fetch the acknowledgments the Client must digitally accept for this offering. Client bearer auth. Fundrise requires the Partner platform to display a checkbox per acknowledgment and require the user to check it to proceed — an automated pas
- Place the investment. Client bearer auth. acknowledgedDocumentIds must carry the documentIds the Client actually accepted in the preceding two steps. On a 500, retrying with the same partnerReferenceId is safe because it is the idempotency
What you'll need to have ready
- partnerReferenceId: Your own opaque unique id for this person. Doubles as the idempotency key for Client creation. Fundrise requires that it contain no PII — do not use an email ad
- primaryEmail
- firstName
- lastName
- taxId: The Client's tax identifier. Sensitive — never log this value.
- dateOfBirth
- address1
- address2
- city
- state
- zip
- country
For your developer
Arazzo workflow fundrise:onboard-client-and-place-investment, 6 operations: $sourceDescriptions.clientsApi.CreateClient → $sourceDescriptions.authenticationApi.GetAccessToken → $sourceDescriptions.offeringsApi.GetOfferings → $sourceDescriptions.offeringsApi.GetOfferingDocuments → $sourceDescriptions.acknowledgmentsApi.GetInvestmentAcknowledgments → $sourceDescriptions.investmentsApi.PlaceInvestment. Specs on APIs.io.