diff --git a/spec/marketing.json b/spec/marketing.json index 9103f2c..3eaa98d 100644 --- a/spec/marketing.json +++ b/spec/marketing.json @@ -26,7 +26,7 @@ }, "automation": { "title": "Automations", - "description": "Mailchimp's classic automations feature lets you build a series of emails that send to subscribers when triggered by a specific date, activity, or event. Use the API to manage Automation workflows, emails, and queues. Does not include Customer Journeys.", + "description": "Mailchimp's classic automations feature lets you build a series of emails that send to subscribers when triggered by a specific date, activity, or event. Use the API to manage Automation workflows, emails, and queues. Does not include Automation flows.", "paths": [ "/automations", "/automations/{workflow_id}", @@ -167,8 +167,8 @@ ] }, "customer-journeys-journeys-steps-actions": { - "title": "Customer Journeys", - "description": "Manage Customer Journey automated workflows", + "title": "Automation flows (Previously Customer Journeys)", + "description": "Manage Automation flows", "paths": [ "/customer-journeys/journeys/{journey_id}/steps/{step_id}/actions/trigger" ], @@ -813,7 +813,7 @@ }, "swagger": "2.0", "info": { - "version": "3.0.85", + "version": "3.0.86", "title": "Mailchimp Marketing API", "contact": { "name": "Mailchimp API Support", @@ -49768,16 +49768,16 @@ "/customer-journeys/journeys/{journey_id}/steps/{step_id}/actions/trigger": { "post": { "summary": "Customer Journeys API trigger for a contact", - "description": "A step trigger in a Customer Journey. To use it, create a starting point or step from the Customer Journey builder in the app using the Customer Journeys API condition. We\u2019ll provide a url during the process that includes the {journey_id} and {step_id}. You\u2019ll then be able to use this endpoint to trigger the condition for the posted contact.", + "description": "A step trigger in an Automation flow. To use it, create a starting point or step from the Automation flow builder in the app using the Customer Journey API condition. We'll provide a url during the process that includes the {journey_id} and {step_id}. You'll then be able to use this endpoint to trigger the condition for the posted contact.", "operationId": "postCustomerJourneysJourneysIdStepsIdActionsTrigger", "parameters": [ { "in": "path", "name": "journey_id", - "x-title": "Journey ID", + "x-title": "Flow ID", "type": "integer", "required": true, - "description": "The id for the Journey." + "description": "The id for the flow." }, { "in": "path", @@ -49794,8 +49794,8 @@ "required": true, "schema": { "type": "object", - "title": "Subscriber in Customer Journey's audience", - "description": "Information about subscribers in a Customer Journey's audience.", + "title": "Subscriber in Automation flow's audience", + "description": "Information about subscribers in a Automation flows's audience.", "required": [ "email_address" ],