accounting/accounts3

accounting/addresses2

accounting/attachments3

accounting/balancesheets2

accounting/cashflowstatements2

accounting/companyinfos2

accounting/contacts3

accounting/creditnotes2

accounting/expenses3

accounting/incomestatements2

accounting/invoices3

accounting/items2

accounting/journalentries3

accounting/payments3

accounting/phonenumbers2

accounting/purchaseorders3

accounting/taxrates2

accounting/trackingcategories2

accounting/transactions2

accounting/vendorcredits2

auth1

connections1

crm/companies3

crm/contacts3

crm/deals3

crm/engagements3

crm/notes3

crm/stages2

crm/tasks3

crm/users2

ecommerce/customers2

ecommerce/fulfillments2

ecommerce/orders3

ecommerce/products3

events1

fieldMappings6

filestorage/files3

filestorage/folders3

filestorage/groups2

filestorage/users2

linkedUsers5

marketingautomation/actions3

marketingautomation/automations3

marketingautomation/campaigns3

marketingautomation/contacts3

marketingautomation/emails2

marketingautomation/events2

marketingautomation/lists3

marketingautomation/messages2

marketingautomation/templates3

marketingautomation/users2

passthrough2

projects2

sync4

ticketing/accounts2

ticketing/attachments3

ticketing/collections2

ticketing/comments3

ticketing/contacts2

ticketing/tags2

ticketing/teams2

ticketing/tickets3

ticketing/users2

webhooks5

ticketing/tickets

Retrieve Tickets

Retrieve Tickets from any connected Ticketing software

get/ticketing/tickets/{id}

Path parameters

idstring required

id of the ticket you want to retrive.

Query parameters

remote_databoolean

Set to true to include data from the original Ticketing software.

Headers

x-connection-tokenstring required

The connection token

Response

namestring nullable required

The name of the ticket

statusstring nullable

The status of the ticket. Authorized values are OPEN or CLOSED.

descriptionstring nullable required

The description of the ticket

due_datestring date-time nullable

The date the ticket is due

typestring nullable

The type of the ticket. Authorized values are PROBLEM, QUESTION, or TASK

parent_ticketstring nullable

The UUID of the parent ticket

completed_atstring date-time nullable

The date the ticket has been completed

prioritystring nullable

The priority of the ticket. Authorized values are HIGH, MEDIUM or LOW.

assigned_tostring[] nullable

The users UUIDs the ticket is assigned to

account_idstring nullable

The UUID of the account which the ticket belongs to

contact_idstring nullable

The UUID of the contact which the ticket belongs to

field_mappingsobject nullable

The custom field mappings of the ticket between the remote 3rd party & Panora

idstring nullable

The UUID of the ticket

remote_idstring nullable

The id of the ticket in the context of the 3rd Party

remote_dataobject nullable

The remote data of the ticket in the context of the 3rd Party

created_atstring date-time nullable

The created date of the object

modified_atstring date-time nullable

The modified date of the object

Example response

{
  "name": "Customer Service Inquiry",
  "status": "OPEN",
  "description": "Help customer",
  "due_date": "2024-10-01T12:00:00Z",
  "type": "BUG",
  "parent_ticket": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
  "collections": [
    "801f9ede-c698-4e66-a7fc-48d19eebaa4f"
  ],
  "tags": [
    "my_tag",
    "urgent_tag"
  ],
  "completed_at": "2024-10-01T12:00:00Z",
  "priority": "HIGH",
  "assigned_to": [
    "801f9ede-c698-4e66-a7fc-48d19eebaa4f"
  ],
  "comment": {
    "body": "Assigned to Eric !",
    "html_body": "<p>Assigned to Eric !</p>",
    "creator_type": "USER",
    "ticket_id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
    "contact_id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
    "user_id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
    "attachments": [
      "801f9ede-c698-4e66-a7fc-48d19eebaa4f"
    ]
  },
  "account_id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
  "contact_id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
  "attachments": [
    "801f9ede-c698-4e66-a7fc-48d19eebaa4f"
  ],
  "field_mappings": {
    "fav_dish": "broccoli",
    "fav_color": "red"
  },
  "id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
  "remote_id": "id_1",
  "remote_data": {
    "key1": "value1",
    "key2": 42,
    "key3": true
  },
  "created_at": "2024-10-01T12:00:00Z",
  "modified_at": "2024-10-01T12:00:00Z"
}

Changes

Changed in 7 of the 18 revisions of this API.791120

Sep 20, 2024be3dc330edf313See the full diff
- ○
  removed the BUG enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the CLOSED enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the CONTACT enum value from the ///// response property for the response status
  response-property-enum-value-removed
- ○
  removed the HIGH enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the LIST enum value from the ////// response property for the response status
  response-property-enum-value-removed
- ○
  removed the LOW enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the MEDIUM enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the OPEN enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the PROJECT enum value from the ////// response property for the response status
  response-property-enum-value-removed
- ○
  removed the SUBTASK enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the TASK enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the TO-DO enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the USER enum value from the ///// response property for the response status
  response-property-enum-value-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 6, 20246502b0fa098c7See the full diff
- ▲
  added subschema #1 to the / response property oneOf list for the response status
  response-property-one-of-added
- ▲
  added subschema #1 to the ////// response property oneOf list for the response status
  response-property-one-of-added
- ▲
  added subschema #1 to the / response property oneOf list for the response status
  response-property-one-of-added
- ▲
  the / response's property type changed from string to no type for status
  response-property-type-changed
- ▲
  the response's property type changed from string to array for status
  response-property-type-changed
- ▲
  the ////// response's property type changed from string to no type for status
  response-property-type-changed
- ▲
  the / response's property type changed from string to no type for status
  response-property-type-changed
Aug 5, 2024ca0fa45ebd0511See the full diff
- ●
  added the new BUG enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new CLOSED enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new CONTACT enum value to the ///// response property for the response status
  response-property-enum-value-added
- ●
  added the new HIGH enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new LOW enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new MEDIUM enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new OPEN enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new SUBTASK enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new TASK enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new TO-DO enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new USER enum value to the ///// response property for the response status
  response-property-enum-value-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 5, 2024ca213ae36b7f351See the full diff
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
- ▲
  the response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
- ○
  the endpoint scheme security bearer was removed from the API
  api-security-removed
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 5, 2024167edd5346ec25See the full diff
- ▲
  the response's property type changed from string to object, and format from date-time to no format for status
  response-property-type-changed
- ▲
  the response's property type changed from string to object, and format from date-time to no format for status
  response-property-type-changed
- ○
  the endpoint scheme security bearer was added to the API
  api-security-added
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
This revision also has 8 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 3, 20249d25bd589fe935See the full diff
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response property became optional for the status
  response-property-became-optional
- ▲
  the response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
- ▲
  the response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 1, 2024414c3e999e0b1See the full diff
- ○
  the endpoint scheme security bearer was removed from the API
  api-security-removed

Full history