API Coverage

Compare API endpoint support across different ticketing platforms. This matrix shows which features are available for each integration.

Filter by capabilities

PaginationFilteringSortingCustom fieldsWebhooks

RESOURCE	Auth	Organizations	Collections	Tickets
Azure DevOps
Bitbucket
GitHub
GitHub Enterprise
GitLab
GitLab (Self-Managed)
Jira
Jira Data Center
Salesforce
ServiceNow
Trello
Linear

Field Mappings

Our unified API standardizes data models across different ticketing providers. Below you can see how Unizo fields map to provider-specific fields for each data model.

Organization

Ticketing project entity.

Unizo Field	Azure DevOps	Bitbucket	GitHub	GitHub Enterprise	GitLab	GitLab (Self-Managed)	Jira	Jira Data Center	Salesforce	ServiceNow	Trello	Linear
idProject ID
loginLogin name
urlProject URL
avatar_urlAvatar URL
descriptionShort description
typeProject type
created_atCreated date
updated_atUpdated date
native_responseNative data

Collections

Ticketing project entity.

Unizo Field	Azure DevOps	Bitbucket	GitHub	GitHub Enterprise	GitLab	GitLab (Self-Managed)	Jira	Jira Data Center	Salesforce	ServiceNow	Trello	Linear
idProject ID
nameProject name
ownerProject owner
access_levelAccess level
descriptionShort description
urlProject URL
created_atCreated date
modified_atModified date
native_responseNative data

Ticket

Issue tracking record.

Unizo Field	Azure DevOps	Bitbucket	GitHub	GitHub Enterprise	GitLab	GitLab (Self-Managed)	Jira	Jira Data Center	Salesforce	ServiceNow	Trello	Linear
idTicket ID
nameTicket name
assigneesAssigned users
creatorTicket creator
due_dateDue date
created_atCreated date
modified_atUpdated date
ticket_typeIssue type
completed_atResolved date
ticket_urlWeb link
accountLinked account
parent_ticketParent issue
issue_linksLinked issues
attachmentsFile links
descriptionTicket body
statusIssue status
priorityIssue priority
native_responseRaw data

Native Provider Field Support

Leveraging nativeResponse

The nativeResponse field enables you to access provider-specific features beyond our unified common data model. This feature allows you to:

• Access provider-specific ticket attributes not included in the common data model
• Implement custom ticketing workflows using native provider capabilities
• Utilize advanced features unique to each ticketing platform
• Maintain compatibility with existing provider-specific integrations

Enterprise Feature

The nativeResponse field is available exclusively for Enterprise and Launch Customer subscriptions. Contact our sales team to upgrade your plan and unlock access to native provider data.

How to Use nativeResponse

{
  "id": "PROJ-123",
  "title": "Fix login issue on mobile app",
  "description": "Users are unable to login on iOS devices",
  "status": "In Progress",
  "priority": "High",
  // ... other unified fields
  "nativeResponse": {
    // Complete provider-specific response
    "fields": {
      "customfield_10001": {
        "value": "iOS",
        "id": "10103"
      },
      "customfield_10002": "2024-Q1",
      "sprint": {
        "id": 23,
        "name": "Sprint 23",
        "state": "active"
      },
      "epic": {
        "id": 10000,
        "key": "PROJ-100",
        "name": "Mobile App Improvements"
      }
    },
    "changelog": {
      "histories": [
        {
          "created": "2024-01-15T09:00:00.000Z",
          "items": [
            {
              "field": "status",
              "fromString": "To Do",
              "toString": "In Progress"
            }
          ]
        }
      ]
    }
  }
}

Need Something More?

Working on a unique ticketing integration? Need extra fields for your issue tracking tools? We're here to help.

Get in touch:

• Email: support@unizo.ai
• Web: Contact Us

We'd love to hear about your use case and help expand our API to meet your needs.