Create contact with the Keap API

Creates a contact and returns it. It needs at least one item in email_addresses, phone_numbers or addresses. With duplicate_option, a matching contact is updated instead of a new one being created.

Identifier
keap_create_contact

The request

POST https://connect.reportei.com/api/tools/keap_create_contact/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "given_name": "<given_name>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
given_namestringNoFirst name.
family_namestringNoLast name.
job_titlestringNoJob title.
email_addressesarrayNoEmail addresses, one per slot.
phone_numbersarrayNoPhone numbers, one per slot.
addressesarrayNoPostal addresses, one per kind.
websitestringNoWebsite address.
owner_idstringNoId of the user who owns the contact, the id field of List users (not global_user_id).
contact_typestringNoType of the contact as configured in the Keap app, for example Lead or Customer.
birth_datestringNoBirth date, for example 1990-05-17.
duplicate_optionstringNoMatch used to find an existing contact to update instead of creating one: by email, by email and name, or by email, name and company. Without it, a new contact is always created.Values: Email, EmailAndName, EmailAndNameAndCompany

Supported connections

Your customer connects their Keap account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/keap, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/keap_create_contact. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.