5 operations. Call each with POST https://app.chirply.io/api/v1/actions/<name> and a bearer token; the response is { "data": { "action", "summary", "result" } }. A read badge means the operation changes nothing; write requires the credential’s write scope.
Create a company
companies.createwrite
Create a company record. Only a name is required; attach contacts to it afterwards with contacts.update.
Parameters
Field
Type
Required
Description
name
string
required
The company name.
domain
string
optional
Primary domain, e.g. 'acme.com'.
phone
string
optional
Main phone number.
website
string
optional
Website URL.
industry
string
optional
Industry.
owner_id
string (uuid)
optional
User id of the team member who owns the relationship.
address
object
optional
Postal address with separate street, city, state, and ZIP / postal code fields.
address.line1
string
optional
Street address.
address.line2
string
optional
Suite / unit.
address.city
string
optional
City.
address.state
string
optional
State or province.
address.postal_code
string
optional
ZIP / postal code.
address.country
string
optional
Country.
notes
string
optional
Free-text notes on the record, visible to the whole account.
custom
map of string → object
optional
Custom-field values keyed by `custom_field_defs.key` (see contacts.list_fields). Replaces the whole blob — send the merged object.
Over MCP the same operation is the tool companies_create at https://app.chirply.io/api/mcp, same bearer token, same input.
Delete a company
companies.deletewriteconfirm
Permanently delete a company and its activity timeline. Contacts at the company are kept but are detached from it. This cannot be undone.
Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.