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 obtaining ticket information, outlining the structure and data types for fields like fulfillment type, expected time, location, price, and contact information.
The JSON object includes fields such as fulfillmentType, expectedFulfillmentTime, location, price, and fulfillmentContact to comprehensively describe ticket fulfillment options.
Each field within the JSON object links to further documentation providing detailed definitions and usage instructions, ensuring developers understand their specific roles and data types.
[[["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 content outlines the JSON representation for receiving tickets, detailing the structure and fields necessary for fulfillment. Key information includes `fulfillmentType` (delivery/pickup), `expectedFulfillmentTime` (time window or ETA), `location` (pickup/delivery address), `price` (cost), and `fulfillmentContact` (user contact details). This JSON format dictates the data required to manage and execute the fulfillment process, whether it be delivery or pickup. Each field corresponds to a specific data object type.\n"]]