Follow up question that can be associated with a survey. The date/time the SegmentColumnSet record was last modified. A single string value that belongs to a picklist, Represents a 64-bit signed integer (used for internal identifiers), A Positive or negative number with or without decimals. All Accounts with the related UserAccount embedded inline. If you use primarily custom fields, make sure to also map at Easily showcase integrations, partners, and apps to your customers. Check the documentation and the syntax of your request and try again. The number of days the Account has been in the journey. The Id of the Contact associated with this Event. Using the provided @odata.nextLink the next page can be retrieved and a new newLink will be provided. Monitoring APIs to guarantee API compliance and data consistency. The number of choices available to answer a survey. The Total Contract Amount of this Account. The data type of the follow up answer. The date/time the JourneyMilestoneProgress record was created. The $orderby option allows resources to be sorted in a particular order. The Id of the Account associated with this Task. The date/time the Event occurred. The Segment must belong to the entity in the request. The Segment must belong to the authorized API User or be configured as a Global Segment. For example, an Account references a UserAccount. 1245) noted at the bottom. The date/time the Segment record was created. The lower-bounds value of the grading scale. Check out the latest new about Apideck and SaaS ecosystems on our blog, Interviews with the leading SaaS companies who are building next-generation platforms and ecosystems. At some later point, if new fields are imported from those Zendesk Tickets they will become available on the exposed endpoint and documented below. The source of the survey response. Projects and tasks themselves cannot interact with plays, journeys, NPS campaigns, or churn scores. ISO 8601 formatted string. You have set up the Teamwork integration. Visit the Schemas section of Churnzero's. The Minimum Event Date for the Event Type. Port OpenAPI Specs to Postman Collections, and inject test suite. Inject tokens at runtime. manager handle Churn Score Calculation available in ChurnZero. This is the template that is used to create an Achievement instance for Accounts that enter the JourneyMilestone. The higher-bounds value of the grading scale. In order to see projects from your Teamwork site in your ChurnZero account, you will need to map this external ID by editing the associated company's name. The Id that this User Account is linked to in an external source. ISO 8601 formatted string. Ready to scale your integration strategy?

You have the option to add this ID to the beginning, end, etc. A subset of the query string options defined in OData v4 are available for use to tailor access to the data in your ChurnZero instance. Surveys related to a Contact. The date/time for the Parent Account's next renewal. Accessed dynamically through Segment Column Set selection. All Accounts ordered by LicenseCount in descending order, then by ObjectLastModifiedDate in ascending order. Every 15 minutes, the sync will pull in new projects and tasks, as well as search through existing projects and tasks in order to match them to contacts and accounts. This is done at the account and/or contact level. The number of Distinct Contacts for the Event Type. Tracking 3,200+ open banking and PSD2 APIs from challenger banks, TPPs, and financial institutions. The Account associated with this progress.

The number of Total Events for the Event Type. This is a one-way sync from Teamwork to ChurnZero: ChurnZero provides a quick link to each project and task in Teamwork, but projects and tasks cannot be edited in ChurnZero. True if the Task Priority is high priority. The Account's status in the JourneyMilestone. The date/time the SegmentColumnSet record was created. You can find the custom fields created for your Churnzero workspace in Admin > Custom Fields then navigating to either the contact or account table.

GET /ChurnScoreCalculation({Id})/ChurnScore. If a different page size is desired, the $top operation can be used in conjunction with $skip. saas smartkarrot The date/time the JourneyProgress record was last modified. If the desired filter cannot be constructed with the available simple or complex operands, then ChurnZero Segments Wrap existing Churnzero API calls with the Apideck Proxy endpoint. True if the Account has failed the JourneyMilestone. multiple resources, they can all be included by referencing the properties with a comma separated list. Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist.

The schema definitions for each object requested or returned from ChurnZero's REST API. The date/time the JourneyMilestoneTask record was last modified. By default, ascending order is utilized unless the direction is specified with desc for descending sort order.

The date/time the JourneyMilestoneAchievement record was last modified. HTTP Basic Authentication can be used with the ChurnZero REST API. ISO 8601 formatted string. ISO 8601 formatted string. You can sync custom tables using Hightouch through Churnzero's batch import API. ISO 8601 formatted string. (Draft, Paused, Running, Complete, Archived), The campaign type of the survey. ISO 8601 formatted string. Inspect all the traffic coming and going to the Churnzero API and optionally inject tokens at runtime. Note: this can be found in the top left of your contact or account page (not the ID in the url). This can happen if you try to read or write to objects or properties that the user does not have access to. ISO 8601 formatted string. The date/time the Contact record was created. Ascending order can be explicitly specified with asc. Accessed dynamically through Segment Column Set selection. Due to the large amounts of data that can be accessed through the REST API, there is a group of Bulk Read Permissions that must be set in order to gain access to the available Entities. Include the total count of Accounts in the query for the Id,Name, and ExternalId of all Accounts. A set of state-the-art unified APIs to build native integrations with other SaaS providers. ISO 8601 formatted string. ISO 8601 formatted string. account ID referenced or a custom field exists or not. The User associated to an Account Role. They are set individually so that access to certain Entities can be controlled on a per-group basis. The ID of the Churn Score associated with this calculation. The underlying model/schema has changed. The date that the response was created. The date/time the JourneyMilestoneStepProgress record was created. The follow up question associated with this survey response. The number of Most Recent Events for the Event Type.

When you create an account, you have the option to enter an External ID. True if the calculation is deemed active. True if the Account has failed the Journey. The number of days this Account is over the expectation for the JourneyMilestone. Records can be matched from your source to your Churnzero workspace by your Churnzero Contact / Account ID. The Id of the Churn Score associated with this Churn Score Factor. Survey response collected in ChurnZero for a Survey.

Once that is done, all projects associated with that company in Teamwork will be mapped to their account in ChurnZero. Read the announcement, Broederminstraat 9, 2018 Antwerp, Belgium. The type of answer associated with the question. The SegmentColumnSet must belong to the entity in the request. The number of requests under the soft max will execute at normal speed. Custom tables may be created by going to the admin tab in Churnzero and selecting "Custom Fields". ISO 8601 formatted string. The day this Journey was evaluated for the Account. Our Developer-friendly plan includes 20,000 API calls per month and is designed to allow a wide range of use cases. The $filter option allows limiting of resources in the collection that is returned for the requested URL. Usually caused by a race condition. Not into REST APIs? ISO 8601 formatted string. The filter is evaluated for each resource in the result set and only those resources that evaluated to true for the given filter will be included in the result. Human-friendly JSON Schema validation for APIs. The Id that this Task is linked to in an external source. The Journey that this JourneyMilestone belongs too. The Event aggregates related to an Entity. Scroll down for code samples, example requests and responses. Select the Id, Name, and ExternalId for all Accounts, Select the Id, Name, and ExternalId for all Accounts and the UserName of related UserAccounts. These properties are automatically added to $select/$expand options where applicable. Accessed dynamically through Segment Column Set selection. Pre-made building blocks to get started with Apideck. True if the Contact has chosen to unsubscribe from marketing emails. To help you track your APIs, Apideck visualises your usage through graphs and history logs. $select can be used in conjunction with $expand to tailor the payload for related resources that are inlined with the response. Available as REST and GraphQL APIs. by name) but is significantly less accurate. Use the application key as your "App Key" in Hightouch. Two thresholds are tracked per minute. The Id of the Contact associated with this Task. ISO 8601 formatted string. ISO 8601 formatted string. Typically this is just a combination of FirstName and LastName. The score that was given for the survey response. If a particular resource is related to The date/time this Account started. Specific Segment ids to use can be discovered either from inside the ChurnZero app or by making a request to the Segment endpoint. Each account in ChurnZero has an external ID. The preferred means of relating a record back to an account is through an ID, specifically the account's External ID. The date/time the Account record was last modified. Query parameters can control the amount and order of the data returned for the resource identified by the URL. The Role related to an Account. The Survey Scores related to an Account. Free form comments associated with the Account failing the Journey. GET /JourneyProgress({Id})/JourneyInstance, GET /JourneyMilestoneProgress({Id})/Account, GET /JourneyMilestoneProgress({Id})/Journey, GET /JourneyMilestoneProgress({Id})/JourneyInstance, GET /JourneyMilestoneProgress({Id})/JourneyMilestone. Not sure how Apideck can help your business? When you view one of the companies in ChurnZero, the associated projects will show up. Similar to using a Segment, using a predefined Segment Column Set in the ChurnZero REST API is achieved by utilizing the Segment Column Set id in a $filter option on an entity that supports Segments. Hightouch supports syncing to the following Churnzero types: Hightouch supports syncing to the following Churnzero objects: Contacts must be associated with an account, and therefore an account external ID must be present in your data.

True if the Segment is globally accessible. The ID of the Contact associated with this survey response. The accessibility of the SegmentColumnSet. Helping you discover the best APIs and SaaS products to integrate with. The date/time for this Account's next renewal. The number of months until the survey reoccurs. The Id of the ChurnScore that is marked as primary for this Account. (Announcement, Email). When there are no more results, an empty result set will be returned. The close date of the Task. Accessed dynamically through Segment Column Set selection. The Journey related to an Account. The Id of the Account associated with this Contact. Collections that support the $orderby operation will list the available resource properties that can be used for ordering. The operating system to build and showcase integrations. The Id of the Account associated with this Event. The date/time the JourneyMilestone record was last modified. The @odata.nextLink provides the URL to retrieve the next page of results. The SegmentColumnSet must belong to the authorized API User or have a configured ShareType of 'All' or 'Domain'. The Maximum Event Date for the Event Type. Accessed dynamically through Segment Column Set selection.

ISO 8601 formatted string. The ID of the Churn Score Factor associated with this calculation. The Contact's combined First Name, Last Name, and Email if available. You can view these requests and response payloads on the logs overview and dashboard. Since Teamwork does not support custom fields on any of these entities so ChurnZero will pull the standard fields for each entity. Visit the documentation and API reference to get a complete overview of the endpoints and APIs we offer. A simple operand would deal with just one property The JourneyInstance assocated with this progress. The number of days since this Account's start date. Documentation based off of the ChurnZero demo customer, MarketingPony. When querying for Accounts you can include the UserAccount in the response if it is defined. Discovering a Segment id (6763) from the URL within the ChurnZero application, Retrieving All available Account Segments via the API, Using a Segment id to retrieve All Accounts that meet the segment criteria for id 6763. The $top option requests the number of resources to be queried in the collection. This is a dynamic API that will adjust as customizations are made to your ChurnZero instance and as new features are developed for ChurnZero. The intent of the soft and hard max thresholds is to coerce an API client into compliance rather than go to an immediate hard error. The Event Type associated to an Event aggregate.

ISO 8601 formatted string. Want to control auth yourself? (Text, YesNo, Currency, Date, Number, Percent, SingleSelect, MultiSelect). The Account that this JourneyInstance belongs too.