Creates a lead, including contact and deal attributes

POST/jsonapi/leads

The externalReference and externalIntegration attributes create a deal reference. externalIntegrationAllowCreate controls creating or reactivating the named integration; it does not prevent duplicate lead submissions. See the external integrations and references guide.

For client-credentials integrations, supply your assigned adviser identifier in the UserId header. See request headers and data access.

Access

Bearer authentication. Confirm your scopes, data access and required adviser context.

Request parameters

No parameters are defined for this operation in the source contract. Authentication and applicable request headers still apply.

Request body

application/vnd.api+json

Example request body

Illustrative request using reviewed sample values. Replace sample values, resource types and IDs with your own. Optional fields are shown for illustration; follow the field descriptions and business rules.

{
  "data": {
    "type": "leads",
    "attributes": {
      "firstName": "Alex",
      "lastName": "Morgan",
      "email": "alex@example.com",
      "mobile": "+61400000000"
    }
  }
}

Request documentobjectLeadDocument ↗

dataobjectrequiredLead ↗

Example request

Use your supplied API base URL and replace path placeholders such as {id}. These examples run in your backend or terminal, where your credentials are kept.

curl --globoff --request POST "${API_BASE_URL}/jsonapi/leads" \
  --header "Authorization: Bearer $ACCESS_TOKEN" \
  --header "UserId: $ADVISER_CONTACT_ID" \
  --header 'Accept: application/vnd.api+json' \
  --header 'Content-Type: application/vnd.api+json' \
  --data '{
  "data": {
    "type": "leads",
    "attributes": {
      "firstName": "Alex",
      "lastName": "Morgan",
      "email": "alex@example.com",
      "mobile": "+61400000000"
    }
  }
}'

Responses

201 response

Response headers

Location — Location of newly created resource

application/vnd.api+json

201 responseobjectLeadDocument ↗

metaobjectread only

jsonApiobjectread only

linksall ofread only

dataobjectrequiredLead ↗

includedarray · nullableread only

For guidance beyond this operation's schema, see troubleshooting and JSON:API explained.