Skip to main content
GET
Zapier Trigger on Person Modification
This endpoint is used by the Portal.io Zapier integration. It fires when a contact (person) record is created, updated, or deleted in your Portal.io account.

Authorizations

X-MSS-API-APPID
string
header
required

Portal application identifier used as part of HMAC-authenticated API requests.

X-MSS-API-USERKEY
string
header
required

Portal user API key used together with the HMAC signature headers.

X-MSS-CUSTOM-DATE
string
header
required

Timestamp header included in the signed request to prevent replay attacks.

X-MSS-SIGNATURE
string
header
required

HMAC-SHA256 signature for the request, calculated over the canonical string defined in the authentication docs.

Headers

Accept
enum<string>
required

Accept Header

Available options:
application/json

Response

Person Item.

Customer contact

id
integer<int32>
required

Unique numeric identifier of the contact

partyType
enum<string>
Available options:
Undefined,
Person,
Company
contactType
enum<string>
Available options:
Undefined,
Client,
Employee,
Contractor,
Other
firstName
string

Contact first name

lastName
string

Contact last name

companyName
string

Company name when the contact represents a company

contactEmail
string

Primary contact email address

contactEmailCC
string

Additional email addresses copied when a proposal is submitted

contactPhone
string

Primary contact phone number

location
PublicLocationModel · object

Location and address details.