Contact API

Contacts are a member's private address book. See Contacts. A contact can also be linked to a group, where it appears as a guest.

Endpoints

Method URI Description
GET /v4/contacts List the member's contacts
POST /v4/contacts Create a contact
GET /v4/contacts/{id} Get one contact
POST /v4/contacts/{id} Update a contact
DELETE /v4/contacts Delete one or more contacts

All v4 responses use the response envelope.

Contact Fields

{
    "name": "John Smith",
    "email": "jsmith@example.com",
    "company_name": "Smith Consulting",
    "personal_number": "5551234567",
    "work_number": "5557654321",
    "website": "https://example.com",
    "address": "123 Main St",
    "city": "Arlington",
    "state": "VA",
    "zipcode": "22201",
    "country": "US",
    "business_category_id": 12,
    "group_id": 306,
    "join_date": "2026-01-15",
    "image": "(file upload)"
}
  • name is required. Everything else is optional.
  • personal_number and work_number are up to 15 characters, and zipcode up to 6.
  • website must be a full URL.
  • image is a JPEG or PNG file up to 12MB, sent as multipart/form-data.
  • group_id stores the contact in a group, where it appears as a guest. The member must belong to that group.

List Contacts

Method URI
GET /v4/contacts

Returns the member's contacts in data.

Create a Contact

Method URI
POST /v4/contacts

Send the contact fields. Returns the new contact.

Update a Contact

Method URI
POST /v4/contacts/{id}

Send the fields you want to change. Updates use POST so that an image file can be included.

Delete Contacts

Method URI
DELETE /v4/contacts 
{
    "contact_ids": [28001, 28002]
}

Deletes several contacts at once. Only the member's own contacts can be deleted. The response includes deleted_count.

Version 3 Endpoints

{warning} Version 3 is deprecated. Use the v4 endpoints above for new work.

Method URI Description
GET /v3/contacts List contacts
GET /v3/contacts/{offset}/{limit} List contacts, one page at a time
POST /v3/contacts Create a contact. If a contact with the same e-mail exists, it is updated instead.
PATCH /v3/contacts/{id} Update a contact
DELETE /v3/contacts/{id} Delete one contact

v3 accepts the same fields as v4, plus referrer_id (the member who invited the contact), and returns the contact object without the envelope.