Create a person
Creates a person. Provide at least a name; link to a company with company.
Email matching. If the request includes an email, Metal checks it against the email and personal email of the contacts Metal can match — people created in Metal or synced from a connected CRM — before creating anything. The comparison ignores case.
- One eligible match: Metal creates no new person. The response returns the existing person with
reused: true. Metal may fill empty fields on that person, such ascurrentTitleorlinkedinUrl, with values from your request. Fields that already have values are not overwritten. A person synced from your CRM is returned unchanged. - Several matches: If more than one match is eligible, Metal creates the new person but holds it for duplicate review. A held person is not written to your CRM until that review is resolved.
- No match, or only ineligible matches: Metal creates the person as usual.
An existing person with the same external reference always takes precedence over an email match.
The response status is 201 in every case. reused: true means the request matched an existing person by email and Metal returned that person. A create that matches an existing external reference also returns that person, with reused omitted, so an absent reused does not prove a new person was created.
Authorizations
The Client ID of your API key.
The secret value of your API key.
Body
Response
The created person, or the existing person Metal returned.
A person returned by POST /v1/people. Adds reused to the standard person.

