Refer a contact to another team

Send one of your team's contacts to another Sure Send team.

  • personId must be a contact already on your team. This endpoint does not
    create contacts; create one first with POST /api/partner/people.
  • receivingTeamId must be another team with active billing. Your own team, or a
    team without active billing, returns 404. See the Referrals section for how
    to get a team's id.
  • sharedFields picks what the receiving team sees, and must name at least one of
    emails, phones, addresses, notes, tags, stage, custom_fields. Unknown names are dropped. The
    contact's name is always shared.
  • When your team requires approval and the API key's user isn't an owner or admin
    (a member's personal key), the referral is created as pending_approval instead
    of pending.
  • A contact can be referred to a given team only once, whatever the earlier
    referral's status.

404 starts Couldn't find Person when personId is missing or not on your team,
and Couldn't find Team when receivingTeamId is missing, your own team, or a team
without active billing.

422 messages you can get:

errorMessageCause
sharedFields must include at least one valid field (…)sharedFields is missing or has no allowed field.
Refer a Lead is turned off for this team. A team owner or admin can turn it on in Settings > Referral Settings.Refer a Lead is turned off for your team.
A referral already exists for this person to this teamThis contact was already referred to this team.
Referral fee type is not included in the listreferralFeeType isn't percentage or flat.
Referral fee percentage is required for percentage fee typepercentage without referralFeePercentage.
Referral fee amount is required for flat fee typeflat without referralFeeAmount.
Referral fee percentage must be greater than 0 / … less than or equal to 100Out of range.
Referral fee amount must be greater than 0 / … less than or equal to 99999999Out of range.
Fee agreement document is required when a referral fee is setYour team requires a signed fee agreement for referral fees. The API can't attach one, so send the referral without a fee, or send it from the app.
Update frequency is not included in the listupdateFrequency isn't weekly, monthly or none.
Referral notes is too long (maximum is 10000 characters)referralNotes is too long.

The saved defaults from GET /api/partner/referralDefaults are not applied
automatically. Send the fee fields you want on each referral.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
uuid
required

A contact on your team.

uuid
required

The team to refer the contact to.

sharedFields
array of strings
required
length ≥ 1

What the receiving team gets a copy of. notes shares the 10 most recent notes.

sharedFields*
Allowed:
string
length ≤ 10000

A note to the receiving team.

string
enum
Defaults to monthly

How often you expect progress updates.

Allowed:
boolean
Defaults to false

Whether the receiving team must post updates at updateFrequency. They get reminders when one is overdue.

string
enum
Allowed:
number

Required when referralFeeType is percentage. Above 0, at most 100.

number

Required when referralFeeType is flat. Above 0.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json