How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vessel Unifications API

The Unifications API from Vessel — 107 operation(s) for unifications.

Vessel Unifications API is one of 37 APIs that Vessel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Unifications. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a GitHub repository.

This API exposes 107 operations across 107 paths, and defines 74 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.vessel.dev.

107 operations 107 paths 74 schemas 107 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.vessel.dev
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Vessel Unifications API declares 1 security scheme for authenticating requests. An API key is passed in the header as vessel-api-token (VesselAPIToken). By default, every request must be authenticated.

Paths & Operations 107

Across 107 paths, the API surfaces 107 operations — 107 POST. Each is listed below with its method, path, parameters, and response codes.

Unifications 107
POST
/api/unifications/chat/users/list
List Users
get-all-users 1 param body → 200
POST
/api/unifications/chat/channels/list
List Channels
get-all-channels 1 param body → 200
POST
/api/unifications/chat/messages/create
Create Message
post-message 1 param body → 200
POST
/api/unifications/chat/messages/update
Update Message
put-message 1 param body → 200
POST
/api/unifications/crm/info/find
Get Connection Info
get-info 1 param → 200
POST
/api/unifications/crm/users/list
List Users
list-users 1 param body → 200
POST
/api/unifications/crm/users/batch-read
Batch Read Users
batch-read-users 1 param body → 200
POST
/api/unifications/crm/users/find
Get User
get-user 1 param body → 200
POST
/api/unifications/crm/users/details
Get User Details
get-details-crm-user 1 param body → 200
POST
/api/unifications/crm/contacts/list
List Contacts
list-contacts 1 param body → 200
POST
/api/unifications/crm/contacts/batch-read
Batch Read Contacts
batch-read-contacts 1 param body → 200
POST
/api/unifications/crm/contacts/find
Get Contact
get-contact 1 param body → 200
POST
/api/unifications/crm/contacts/create
Create Contact
create-contact 1 param body → 200
POST
/api/unifications/crm/contacts/update
Update Contact
update-contact 1 param body → 200
POST
/api/unifications/crm/contacts/details
Get Contact Details
get-details-crm-contact 1 param body → 200
POST
/api/unifications/crm/deals/list
List Deals
list-deals 1 param body → 200
POST
/api/unifications/crm/deals/batch-read
Batch Read Deals
batch-read-deals 1 param body → 200
POST
/api/unifications/crm/deals/find
Get Deal
get-deal 1 param body → 200
POST
/api/unifications/crm/deals/create
Create Deal
create-deal 1 param body → 200
POST
/api/unifications/crm/deals/update
Update Deal
update-deal 1 param body → 200
POST
/api/unifications/crm/deals/details
Get Deal Details
get-details-crm-deal 1 param body → 200
POST
/api/unifications/crm/accounts/list
List Accounts
list-accounts 1 param body → 200
POST
/api/unifications/crm/accounts/batch-read
Batch Read Accounts
batch-read-accounts 1 param body → 200
POST
/api/unifications/crm/accounts/find
Get Account
get-account 1 param body → 200
POST
/api/unifications/crm/accounts/create
Create Account
create-account 1 param body → 200
POST
/api/unifications/crm/accounts/details
Get Account Details
get-details-crm-account 1 param body → 200
POST
/api/unifications/crm/leads/list
List Leads
list-leads 1 param body → 200
POST
/api/unifications/crm/leads/batch-read
Batch Read Leads
batch-read-leads 1 param body → 200
POST
/api/unifications/crm/leads/find
Get Lead
get-lead 1 param body → 200
POST
/api/unifications/crm/leads/create
Create Lead
create-lead 1 param body → 200
POST
/api/unifications/crm/leads/update
Update Lead
update-lead 1 param body → 200
POST
/api/unifications/crm/custom-fields/create
Create Custom Field
create-lead-custom-field 1 param body → 200
POST
/api/unifications/crm/leads/details
Get Lead Details
get-details-crm-lead 1 param body → 200
POST
/api/unifications/crm/notes/list
List Notes
list-notes 1 param body → 200
POST
/api/unifications/crm/notes/batch-read
Batch Read Notes
batch-read-notes 1 param body → 200
POST
/api/unifications/crm/notes/find
Get Note
get-note 1 param body → 200
POST
/api/unifications/crm/notes/create
Create Note
create-note 1 param body → 200
POST
/api/unifications/crm/notes/update
Update Note
update-note 1 param body → 200
POST
/api/unifications/crm/notes/details
Get Note Details
get-details-crm-note 1 param body → 200
POST
/api/unifications/crm/tasks/list
List Tasks
list-tasks 1 param body → 200
POST
/api/unifications/crm/tasks/batch-read
Batch Read Tasks
batch-read-tasks 1 param body → 200
POST
/api/unifications/crm/tasks/find
Get Task
get-task 1 param body → 200
POST
/api/unifications/crm/tasks/create
Create Task
create-task 1 param body → 200
POST
/api/unifications/crm/tasks/update
Update Task
update-task 1 param body → 200
POST
/api/unifications/crm/tasks/details
Get Task Details
get-details-crm-task 1 param body → 200
POST
/api/unifications/crm/events/list
List Events
list-events 1 param body → 200
POST
/api/unifications/crm/events/batch-read
Batch Read Events
batch-read-events 1 param body → 200
POST
/api/unifications/crm/events/find
Get Event
get-event 1 param body → 200
POST
/api/unifications/crm/events/create
Create Event
create-event 1 param body → 200
POST
/api/unifications/crm/events/update
Update Event
update-event 1 param body → 200
POST
/api/unifications/crm/events/details
Get Event Details
get-details-crm-event 1 param body → 200
POST
/api/unifications/crm/attendees/list
List Event Attendees
list-event-attendees 1 param body → 200
POST
/api/unifications/crm/attendees/batch-read
Batch Read Event Attendees
batch-read-event-attendees 1 param body → 200
POST
/api/unifications/crm/attendees/find
Get Event Attendee
get-event-attendee 1 param body → 200
POST
/api/unifications/crm/attendees/create
Create Event Attendee
create-event-attendee 1 param body → 200
POST
/api/unifications/crm/attendees/update
Update Event Attendee
update-event-attendee 1 param body → 200
POST
/api/unifications/crm/attendees/details
Get Attendee Details
get-details-crm-attendee 1 param body → 200
POST
/api/unifications/crm/emails/list
List Emails
list-emails 1 param body → 200
POST
/api/unifications/crm/emails/batch-read
Batch Read Emails
batch-read-emails 1 param body → 200
POST
/api/unifications/crm/emails/find
Get Email
get-email 1 param body → 200
POST
/api/unifications/crm/emails/create
Create Email
create-email 1 param body → 200
POST
/api/unifications/crm/emails/update
Update Email
update-email 1 param body → 200
POST
/api/unifications/crm/emails/details
Get Email Details
get-details-crm-email 1 param body → 200
POST
/api/unifications/crm/calls/list
List Calls
list-calls 1 param body → 200
POST
/api/unifications/crm/calls/batch-read
Batch Read Calls
batch-read-calls 1 param body → 200
POST
/api/unifications/crm/calls/find
Get Call
get-call 1 param body → 200
POST
/api/unifications/crm/calls/create
Create Call
create-call 1 param body → 200
POST
/api/unifications/crm/calls/update
Update Call
update-call 1 param body → 200
POST
/api/unifications/crm/calls/details
Get Call Details
get-details-crm-call 1 param body → 200
POST
/api/unifications/crm/lists/list
List Lists
list-lists 1 param body → 200
POST
/api/unifications/crm/lists/find
Get List
get-list 1 param body → 200
POST
/api/unifications/crm/lists/details
Get List Details
get-details-crm-list 1 param body → 200
POST
/api/unifications/dialer/users/list
List Users
get-all-users 1 param body → 200
POST
/api/unifications/dialer/users/find
Get User
get-one-user 1 param body → 200
POST
/api/unifications/dialer/contacts/list
List Contacts
get-all-contacts 1 param body → 200
POST
/api/unifications/dialer/contacts/find
Get Contact
get-one-contact 1 param body → 200
POST
/api/unifications/dialer/contacts/create
Create Contact
post-contact 1 param body → 200
POST
/api/unifications/dialer/contacts/update
Update Contact
put-contact 1 param body → 200
POST
/api/unifications/dialer/calls/list
List Calls
get-all-calls 1 param body → 200
POST
/api/unifications/dialer/calls/find
Get Call
get-one-call 1 param body → 200
POST
/api/unifications/dialer/calls/start
Start a Call
start-call 1 param → 200
POST
/api/unifications/engagement/users/list
List Users
get-all-users 1 param body → 200
POST
/api/unifications/engagement/users/find
Get User
get-one-user 1 param body → 200
POST
/api/unifications/engagement/accounts/list
List Accounts
get-all-accounts 1 param body → 200
POST
/api/unifications/engagement/accounts/find
Get Account
get-one-account 1 param body → 200
POST
/api/unifications/engagement/accounts/create
Create Account
post-account 1 param body → 200
POST
/api/unifications/engagement/contacts/list
List Contacts
get-all-contacts 1 param body → 200
POST
/api/unifications/engagement/contacts/find
Get Contact
get-one-contact 1 param body → 200
POST
/api/unifications/engagement/contacts/create
Create Contact
post-contact 1 param body → 200
POST
/api/unifications/engagement/contacts/update
Update Contact
put-contact 1 param body → 200
POST
/api/unifications/engagement/contacts/list-custom-fields
List Custom Fields
get-all-customFields 1 param body → 200
POST
/api/unifications/engagement/contacts/create-custom-field
Create Custom Field
post-customFields 1 param body → 200
POST
/api/unifications/engagement/emails/list
List Emails
get-all-emails 1 param body → 200
POST
/api/unifications/engagement/emails/find
Get Email
get-one-email 1 param body → 200
POST
/api/unifications/engagement/sequences/list
List Sequences
get-all-sequences 1 param body → 200
POST
/api/unifications/engagement/sequence/start
Start Sequence
post-start-sequence 1 param body → 200
POST
/api/unifications/engagement/sequences/create
Create Sequence
post-sequences 1 param body → 200
POST
/api/unifications/engagement/sequence-steps/batch-create
Batch Create Sequence Steps
post-sequences-steps 1 param body → 200
POST
/api/unifications/engagement/mailboxes/list
List Mailboxes
get-all-mailboxes 1 param body → 200
POST
/api/unifications/engagement/tags/list
List Tags
get-all-tags 1 param body → 200
POST
/api/unifications/marketing/users/list
List Users
get-all-users 1 param body → 200
POST
/api/unifications/marketing/contacts/list
List Contacts
get-all-contacts 1 param body → 200
POST
/api/unifications/marketing/contacts/find
Find Contact
get-one-contact 1 param body → 200
POST
/api/unifications/marketing/contacts/create
Create Contact
post-contact 1 param body → 200
POST
/api/unifications/marketing/contacts/update
Update Contact
put-contact 1 param body → 200
POST
/api/unifications/marketing/lists/list
List Lists
get-all-lists 1 param body → 200
POST
/api/unifications/marketing/lists/find
Find List
get-one-list 1 param body → 200

Schemas 74

The contract defines 74 schemas that model the data the API accepts and returns. The most detailed are Email (17 properties), Call_2 (16 properties), Contact_3 (16 properties), Deal (14 properties). Each schema is shown below with its type and property counts.

IncludeFields
object
1 property
User
object
5 properties 2 required
Channel
object
4 properties 2 required
DateFilter
object
8 properties
StringListFilter
object
4 properties
Contact
object
Information about an individual affiliated with another CRM Object (e.g., a Lead, a Deal, etc)
11 properties 4 required
ListWithAssociations
object
A List or View in a CRM
6 properties 5 required
ContactUpdate
object
Update a Contact.
8 properties
LeadUpdate
object
8 properties
SyncedCache
boolean
If true, will hit the [synced-cache](/pages/home/synced-cache)
NoteCreate
object
Create a new Note. You may only associate a note with at most one entity of each type upon creation.
4 properties
DealCreate
object
7 properties 2 required
AccountCreate
object
10 properties 1 required
Address
object
5 properties
Deal
object
(Alias: Opportunity) An object representing either the opportunity to sell a product to an Account, or in the case of an isWon deal, a product sold to an Accou…
14 properties 6 required
Task
object
A task attached to some CRM object
11 properties 4 required
BooleanFilter
object
2 properties
Email
object
An email is a message sent from one person to another through an email service. Emails involve participants - the person who the email was sent to, or the pers…
17 properties 7 required
CallCreate
object
7 properties 3 required
EmailUpdate
object
4 properties
EventUpdate
object
9 properties
Lead
object
A Lead represents an individual, or sometimes an organization, that is interested in purchasing your product (i.e., is a potential Deal). CRM Caveats: - HubSpo…
12 properties 4 required
EventAttendee
object
Event Attendees hold information about someone who attendee or was invited to an event. Attendees are always associated with some Event and another person obje…
8 properties 5 required
DealUpdate
object
7 properties 1 required
StringFilter
object
8 properties
Note
object
A Note attached to some CRM Object.
7 properties 4 required
ContactCreate
object
Properties that a contact can be created with
8 properties 1 required
EventAttendeeCreate
object
5 properties 2 required
CustomFieldCreate
object
5 properties 2 required
Event
object
Events are a type of activity that has attendees and takes place at a certain point in time (i.e., has a start and end date). For the currently supported CRMs,…
12 properties 4 required
EmailCreate
object
12 properties 3 required
EventAttendeeUpdate
object
2 properties
Field
object
(Alias: property) A field is a key-value pair on a CRM Object that provides information about that object.
11 properties 8 required
CallUpdate
object
3 properties 1 required
LeadCreate
object
8 properties 1 required
User_2
object
Users of the connected CRM platform. These are not the contacts or leads, but rather the user accounts from the connected CRM.
7 properties 4 required
NativeData
object
Native fields for the connected platform. For reads, this object is only returned if the include.$native field is set to true in the request body.
Call
object
10 properties
EventCreate
object
9 properties 2 required
NoteUpdate
object
Update an existing Note. Please note that updating associations is not currently supported.
4 properties
Account
object
(Alias: company, organization) An organization involved with your business.
13 properties 4 required
NumberFilter
object
8 properties
TaskUpdate
object
8 properties
TaskCreate
object
8 properties
ListWithoutAssociations
object
A List or View in a CRM
5 properties 4 required
Contact_2
object
9 properties 3 required
User_3
object
Users of the connected Dialer. These are not the contacts, but rather the user accounts from the connected Dialer.
9 properties 2 required
Call_2
object
16 properties 3 required
Phone
object
2 properties
ContactCreate_2
object
8 properties 2 required
Contact_3
object
An known individual affiliated with an Account, Deal, etc
16 properties 4 required
ContactUpdate_2
object
Properties that a contact can be updated with
6 properties
SequenceStart
object
Start a sequence
3 properties
Sequence
object
Properties that a sequence can be created with
13 properties
AccountCreate_2
object
Properties that an account can be created with
8 properties 1 required
Address_2
object
7 properties
Email_2
object
A email between a User and an external Contact
11 properties 4 required
SequenceCreate
object
3 properties 2 required
ContactCreate_3
object
Properties that a contact can be created with
7 properties
ContactCustomFieldCreate
object
2 properties 1 required
EmailAddress
object
4 properties
SequenceStepSettingsCreate
object
5 properties
Tag
object
A tag or label used to categorize objects.
5 properties 1 required
Mailbox
object
Mailboxes in the connected Engagement platform. These are email accounts that outbound emails will be sent from.
7 properties
SequenceStepCreate
object
properties that a sequence step can be created with
5 properties 4 required
User_4
object
Users of the connected Engagement platform. These are not the contacts or leads, but rather the user accounts from the connected Engagement Platform.
7 properties 3 required
ContactCustomField
object
4 properties 2 required
Account_2
object
(Alias: company, organization) An organization involved with your business.
13 properties 4 required
Phone_2
object
4 properties
Contact_4
object
8 properties 3 required
ContactUpdate_3
object
6 properties 3 required
User_5
object
7 properties 3 required
List
object
5 properties 3 required
ContactCreate_4
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vessel-unifications-api-openapi.yml Raw ↑

Other APIs Vessel publishes across the network.

Vessel Accounts API
Vessel Actions API
Vessel Attendees API
Vessel Auth API
Vessel Connection API
Vessel Connections API
Vessel Contact Custom Fields API
Vessel Contacts API
Vessel CRM API
Vessel Deals API
Vessel Emails API
Vessel Eng Accounts API
Where this information came from

This is an independent, third-party profile of Vessel Unifications API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.