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
| Parameter | Type | Required | Description |
|---|---|---|---|
| given_name | string | No | First name. |
| family_name | string | No | Last name. |
| job_title | string | No | Job title. |
| email_addresses | array | No | Email addresses, one per slot. |
| phone_numbers | array | No | Phone numbers, one per slot. |
| addresses | array | No | Postal addresses, one per kind. |
| website | string | No | Website address. |
| owner_id | string | No | Id of the user who owns the contact, the id field of List users (not global_user_id). |
| contact_type | string | No | Type of the contact as configured in the Keap app, for example Lead or Customer. |
| birth_date | string | No | Birth date, for example 1990-05-17. |
| duplicate_option | string | No | Match 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.
Other Keap tools
- List contactsGETLists the contacts of the Keap app in contacts, with next_page_token for the following page. Without fields, each contact comes with a default set of properties. Filter by email, name, ids and other fields with filter.
- Update contactPATCHUpdates the fields sent and returns the contact. Fields left out keep their values, but each list sent (email_addresses, phone_numbers, addresses) replaces the whole list.
- List tagsGETLists the tags of the Keap app in tags, with id, name, description and category, and next_page_token for the following page.
- Create tagPOSTCreates a tag and returns it with its id. The tag is not applied to anyone until Apply tag.
- Apply tagPOSTApplies a tag to one or more contacts. Applying a tag can start the automations of the Keap app that listen to it, such as email sequences.
- Remove tagPOSTRemoves a tag from one or more contacts. The tag itself stays in the Keap app.
- List opportunitiesGETLists the opportunities of the sales pipeline in opportunities, each with its contact, stage and user, and next_page_token for the following page.
- Create opportunityPOSTCreates an opportunity for a contact in a pipeline stage and returns it. opportunity_title, contact_id and stage_id are required.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
