ticketing/teams

Retrieve Teams from any connected Ticketing software

get/ticketing/teams/{id}

Request

  • Base URL
    https://api.panora.dev
  • URL
    https://api.panora.dev/ticketing/teams/{id}
  • Auth
    API key in header x-api-key

Path parameters

idstring required

id of the team you want to retrieve.

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 team

descriptionstring nullable

The description of the team

field_mappingsobject nullable

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

idstring nullable

The UUID of the team

remote_idstring nullable

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

remote_dataobject nullable

The remote data of the team 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": "My team",
  "description": "Internal members",
  "field_mappings": {
    "fav_dish": "broccoli",
    "fav_color": "red"
  },
  "id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
  "remote_id": "id_1",
  "remote_data": {
    "fav_dish": "broccoli",
    "fav_color": "red"
  },
  "created_at": "2024-10-01T12:00:00Z",
  "modified_at": "2024-10-01T12:00:00Z"
}

Changes

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became optional for the status

    • breaking

      the response property became optional for the status

    • breaking

      the response property became optional for the status

    • breaking

      the response property became optional for the status

    • breaking

      the response's property type changed from object to string, and format from no format to date-time for status

    • breaking

      the response's property type changed from object to string, and format from no format to date-time for status

    • info

      the endpoint scheme security bearer was removed from the API

    • breaking

      the response's property type changed from string to object, and format from date-time to no format for status

    • breaking

      the response's property type changed from string to object, and format from date-time to no format for status

    • info

      the endpoint scheme security bearer was added to the API

    • info

      the response property became required for the status

    • info

      the response property became required for the status

    • info

      the response property became required for the status

    • info

      the response property became required for the status