Updated ActionTag gender query string options
Added
56 • Not Listed
57 • Third Gender
58 • Cisgender Male
59 • Cisgender Female
Added
56 • Not Listed
57 • Third Gender
58 • Cisgender Male
59 • Cisgender Female
The /people/{vanId}/canvassResponses (or /people/{personIdType}:{personId}/canvassResponses ) endpoint will now require canvassContext.phone.phoneNumber when canvassContext.inputTypeId is 1 (Phone) or 37 (SMS).
Added the following ActionTag race query string options:
25 • Not Listed
26 • Asian or Asian American
27 • White
Removed the following ActionTag race query string options:
1 • Asian
3 • Caucasian or White
Added the following ActionTag sexual orientation query string options:
25 • Not Listed
The /people/{vanId}/canvassResponses (or /people/{personIdType}:{personId}/canvassResponses ) endpoint is your go-to for applying Activist Codes to people. You can now use this endpoint to assign an Activist Code without creating a corresponding Contact History record by setting omitActivistCodeContactHistory on the optional canvassContext property to true. This will work as long as all responses in the response array are of type ActivistCode.
Added support for Disbursements at Custom Fields.
The Saved Lists endpoint accepts pagination parameters, but until now was not respecting them and would only return the first page of randomly-ordered results. This has been fixed, and the endpoint now respects both the $top and $skip parameters and orders by the savedListId property, allowing retrieving all Saved Lists.
Added support for phonesFile Action Type and a new /fileLoadingJobs/{jobId}/stats endpoint for checking results.
By popular request, you can now see the subject of each email you sent out.
Added documentation for ActionTag Email Signup and SMS Signup query strings