Transactions API will be deprecated on May 3, 2023, ahead of the Conversational Actions sunset on June 13, 2023. For more information, see Conversational Actions sunset.
Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
This documentation details the JSON representation for retrieving ticket information, outlining the structure and data types for fulfillment details.
The JSON object includes fields like fulfillment type, expected fulfillment time, location, price, and contact information.
Each field within the JSON object has a specific data type and provides details regarding the ticket fulfillment process, such as delivery or pickup options, timeframes, and associated costs.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[],["The provided JSON structure defines how to represent ticket fulfillment information. Key details include `fulfillmentType` (delivery or pickup), `expectedFulfillmentTime` (time window or ETA), `location` (pickup or delivery point), `price` (cost), and `fulfillmentContact` (user contact details). These fields use specific object types and an enum for specifying the nature of the fulfillment, timing, place, price and user.\n"]]