openapi: 3.2.0 info: title: atVenu Tickets API version: '2026-09-26' description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-09-26: 45 operation(s) read from 31 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; atVenu has published no machine-readable contract that the pipeline could find. Engine: local.' x-evidence-tiers: code-example: 43 documentation: 2 pages-with-code: 29 pages-read: 31 x-generated-from: documentation x-provenance: generated x-authored-by: API Evangelist x-generated: '2026-09-26' x-generator: generate-contract-from-docs.py x-engine: local x-sources: - https://developer.zendesk.com/documentation/developer-tools/working-with-the-zendesk-apis/exploring-zendesk-apis-with-postman - https://developer.zendesk.com/documentation/ticketing/events/getting-started-with-events - https://developer.zendesk.com/documentation/ticketing/profiles/getting-started-with-profiles - https://developer.zendesk.com/documentation/custom-data/custom-objects/getting-started-with-custom-objects - https://developer.zendesk.com/documentation/developer-tools/getting-started/getting-a-trial-or-sponsored-account-for-development - https://developer.zendesk.com/api-reference/ticketing/introduction - https://developer.zendesk.com/api-reference/status_api/status_api - https://developer.zendesk.com/api-reference/live-chat/chat-conversations-api/conversations-api - https://developer.zendesk.com/api-reference/integration-services/configs/configs - https://developer.zendesk.com/api-reference/integration-services/connections/all_connections - https://developer.zendesk.com/api-reference/integration-services/inbound-webhooks/inbound_webhooks - https://developer.zendesk.com/api-reference/integration-services/links/links - https://developer.zendesk.com/api-reference/integration-services/registry/bundles - https://developer.zendesk.com/documentation/webhooks/creating-and-monitoring-webhooks - https://developer.zendesk.com/documentation/event-connectors/webhooks/creating-and-monitoring-webhooks - https://developer.zendesk.com/documentation/api-basics/getting-started/getting-a-trial-or-sponsored-account-for-development - https://developer.zendesk.com/documentation/api-basics/getting-started/installing-and-using-curl - https://developer.zendesk.com/documentation/api-basics/getting-started/exploring-zendesk-apis-with-postman - https://developer.zendesk.com/documentation/api-basics/best-practices/best-practices-for-avoiding-rate-limiting - https://developer.zendesk.com/documentation/api-basics/working-with-data/working-with-json - https://developer.zendesk.com/documentation/api-basics/working-with-data/searching-with-the-zendesk-api - https://developer.zendesk.com/documentation/api-basics/working-with-data/side_loading - https://developer.zendesk.com/documentation/api-basics/working-with-data/using-the-incremental-export-api - https://developer.zendesk.com/documentation/api-basics/working-with-data/exporting-users - https://developer.zendesk.com/documentation/api-basics/working-with-data/importing-users-with-the-zendesk-api - https://developer.zendesk.com/documentation/api-basics/working-with-data/exporting-access-logs - https://developer.zendesk.com/documentation/api-basics/pagination/paginating-through-lists-using-cursor-pagination - https://developer.zendesk.com/documentation/api-basics/pagination/paginating-through-lists-using-offset-pagination - https://developer.zendesk.com/documentation/api-basics/pagination/paginating-through-lists - https://developer.zendesk.com/documentation/api-basics/pagination/understanding-the-limitations-of-offset-pagination - https://developer.zendesk.com/documentation/api-basics/working-with-the-zendesk-apis/exploring-zendesk-apis-with-postman servers: - url: https://support.zendesk.com security: - bearer: [] tags: - name: Tickets paths: /api/v2/tickets/3.json: get: operationId: get_api_v2_tickets_3_json tags: - Tickets summary: GET /api/v2/tickets/3.json x-source: https://developer.zendesk.com/api-reference/ticketing/introduction responses: '200': description: Success (shape read from the example response on the page) content: application/json: schema: $ref: '#/components/schemas/GetApiV2Tickets3JsonResponse' x-evidence: kind: code-example language: curl snippet: "curl https : / / { subdomain } . zendesk . com / api / v2 / tickets . json \\ - d '{\"ticket\": {\"subject\": \"Printer offline\", \\ \"comment\": { \"body\": \"My printer is offline. Restarting doesn’t help.\" }}}' \\ - H \"Content-Type: application/json\" - H \"Idempotency-Key: 12345\" \\ - v - u user : password - X POST \n This creates the following response, which also includes a x-idempotency-lookup: miss header:" components: schemas: GetApiV2Tickets3JsonResponse: type: object properties: ticket: type: object properties: url: type: string id: type: integer subject: type: string securitySchemes: bearer: type: http scheme: bearer