Unified.to | Real-time Unified API for all B2B SaaS - Unified.to

Unified

Integration: Zendesk
Back to integrations

Overview

Company website:

https://zendesk.com

Integration launch date:

January 12, 2023

API Categories:

Ticketing Authentication HR Passthrough

API Authorization:

OAuth2 flow

MESSAGING CHANNEL

End-API object:

topic

Unified API Methods:

List options:

Readable fields:

id name web_url

Writable fields:

MESSAGING MESSAGE

End-API object:

post comment

Unified API Methods:

Webhooks:

Virtual Native

List options:

Readable fields:

author_member id message parent_message_id

Writable fields:

KMS PAGE

End-API object:

article

Unified API Methods:

Webhooks:

Virtual Native

List options:

Readable fields:

download_url id space_id title type user_id

Writable fields:

KMS SPACE

End-API object:

section category

Unified API Methods:

List options:

Readable fields:

description id name parent_id parent_space_id

Writable fields:

HRIS GROUP

End-API object:

group

Unified API Methods:

List options:

limit offset user_id

Readable fields:

created_at description id is_active name type updated_at user_ids

Slow fields:

Writable fields:

HRIS EMPLOYEE

End-API object:

user

Unified API Methods:

Webhooks:

Virtual Native

List options:

Readable fields:

created_at emails employee_number employee_roles employment_status first_name id image_url language_locale last_name name telephones timezone updated_at

Writable fields:

TICKETING CUSTOMER

End-API object:

user

Unified API Methods:

List Get Create Update Remove

Webhooks:

Virtual Native

List options:

Readable fields:

created_at emails id name tags telephones updated_at

Writable fields:

emails name tags telephones

TICKETING NOTE

End-API object:

comment

Unified API Methods:

Webhooks:

Virtual

List options:

ticket_id limit offset order sort_by_created_at sort_by_updated_at

required filter

Readable fields:

created_at customer_id description id user_id

Writable fields:

ticket_id customer_id description user_id

required fields

TICKETING TICKET

End-API object:

ticket

Unified API Methods:

List Get Create Update Remove

Webhooks:

Virtual

List options:

limit offset order sort_by_created_at sort_by_name sort_by_updated_at

Readable fields:

closed_at created_at customer_id description id priority status subject tags updated_at url

Writable fields:

description priority status subject tags

PASSTHROUGH

Unified API Methods:

POST GET PUT DELETE

List options:

Readable fields:

Writable fields:

Are we missing anything? Let us know

Was this page helpful?