Skip to main content
GET
Zapier Trigger for Proposal Status Change
This endpoint is used by the Portal.io Zapier integration. It fires when a proposal’s status changes in your Portal.io account — for example, when a proposal moves from Draft to Submitted, or from Submitted to Accepted. Each Zapier subscription can filter by specific statuses so that your Zap only triggers on transitions you care about.

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

Proposal List.

ZapierProposalItem

id
integer<int32>
required
name
string
number
integer<int32>
status
enum<string>
Available options:
Undefined,
Draft,
Submitted,
ViewedByClient,
Accepted,
Declined,
Delayed,
Completed,
EmailFailed,
Expired
total
null | number<double>
customer
PublicCustomerModel · object

Customer contact

proposalPdf
null | string
proposalCsv
null | string
installerPdf
null | string
salesPerson
null | string
salesPersonEmail
null | string
areas
PublicAreaModel · object[]
financialSummary
PublicFinancialSummaryModel · object

Financial totals, discounts, tax, and currency values for the proposal

profit
PublicProfitModel · object

Profit summary for the proposal

recurringServices
PublicRecurringServicesModel · object

Recurring service summary associated with the proposal.

changeOrders
PublicChangeOrderModel · object[]