Onboarding Gestion des absences Gestion du temps Présences & badgeages Notes de frais Performance & objectifs Documents & signatures App mobile Libre-service employé
L'entreprise Carrières Sécurité Contact
Entreprises moyennes Petites entreprises Grandes entreprises Partenaires SIRH Suisse SIRH France
Blog Centre d'aide Références clients Presse Panorama SIRH Notes de frais mondiales Absences mondiales Roadmap
Plans Connexion Essai 30 jours gratuit
Skip to content
Illizeo

Core HR Services

Personnel Administration

Files, contracts and centralized data.

People Analytics

Real-time HR dashboards.

Storage & Signature

Documents and electronic signature.

Company documents

Policies, rules and guides, targeted.

Mandatory notices

Legal notices, online.

Bulk signature

Signature campaigns and employee documents.

Project Management

Track cross-functional HR projects.

Modules

HR Requests

Service desk, deadlines, tracking

Help desk

Internal and external tickets, committed times.

Survey

Engagement, pulse and onboarding surveys.

Whistleblowing

Confidential reporting, Sapin 2 & EU compliant.

Recruitment

Requisitions, ATS, pipeline, interviews.

Employee referral

Referrals, tracking and bonuses.

Expense Reports

Capture, validation and reimbursement.

Benefits

Meal vouchers, mobility, well-being

Budget & payroll costs

Budget, salary review, pay equity.

CRM

Accounts, pipeline, quotes, commissions.

 

BDESE

French economic and social database.

Flex Office

Desk booking and hybrid attendance.

Scheduling

Team rosters, shifts and open shifts.

Time Management

Absences, attendance, badging.

Absences Attendance ZKTeco Ultima time clocks Choosing your clocking method

Performance & Objectives

Continuous reviews and aligned OKRs.

Training & skills

Skills, plan, sessions, certifications.

Onboarding & OffBoarding

Automated onboarding and offboarding journeys.

Platform

Emails

Templates, personalization, deliverability.

Employee Self-Service

Personal space for each employee.

Workflows & Approvals

No-code configurable workflows.

Alerts & Notifications

Stay informed in real time.

Mobile App

iOS and Android, offline.

Security & Compliance

ISO 27001, GDPR, SSO.

 

Permissions & Roles

Granular access control.

Governance & Security

History, audit trail, SoD, security by design.

Laws & agreements

Built-in collective agreements, more on request.

Connectors

SSO, payroll, calendar, e-signature: 22 tools.

REST API

Scoped tokens, OpenAPI.

Webhooks

Signed HR events, auto retries.

SFTP exports

Scheduled reports dropped on your server.

Salaries

Swiss payroll

Payroll, withholding tax, certificates.

Preliminary Salaries

Payroll preparation and control.

Outsourced Salaries

Payroll delegated to our experts.

Global Payroll Consolidated

Multi-country, multi-currency.

Consulting

Illizeo Premium Consulting

Tailor-made HR support.

New

Regulatory Compliance in 1 click

Stay automatically up to date with local and international legal changes.

Discover →
Integrations

About us

Our mission, our teams.

Customers

100+ customers trust us.

Press

Articles, awards, press releases.

Careers

Join the Illizeo adventure.

Contact

Let us discuss your project.

By company size

Small Businesses

Get started in under 30 days.

Medium-sized Companies

Manage multiple sites simultaneously.

Large Companies

Multi-country compliance and SSO.

Organizations & Public Sector

Advanced regulatory reporting.

Partnerships

Become an integrator or reseller.

By country

HRIS Switzerland

Withholding tax, BVG/LPP, FADP.

HRIS France

Agreements, leave, BDESE.

Blog

HR insights and product updates.

Help Center

Step-by-step guides and FAQ.

Roadmap

What's coming in Illizeo.

Family allowances

Global HR guide - 147 countries.

Pricing
Login Try for free →

Book a meeting with Illizeo

Pick a slot in the calendar below.

Core HR services

25
  • People Analytics
    • Permissions and data confidentiality
    • Scheduling a report
    • Describing your report to the AI
    • Creating a custom report
    • System reports catalogue
    • System reports
    • The Employee Analytics dashboard
    • Getting started with People Analytics
  • Storage & e-signature
    • Replacing, unpublishing or deleting a document
    • Publishing a company document and choosing its audience
    • Reading and searching company documents
    • Getting started with company documents
  • HR project management
    • Project settings and finances
    • Managing a project team
    • Planning a project and measuring time spent
    • Organising a project’s tasks
    • Monitoring a project from the Overview
    • Getting started with project management
  • Mandatory notices
    • Publishing and withdrawing mandatory display documents
    • Getting started with mandatory display
  • HR access
    • Entering an absence for a whole population
    • Tracking a signature campaign
    • Launching a signature campaign
    • Finding the documents of your whole population
    • Getting started with HR access

Payroll

26
  • Preliminary salaries
    • Payroll settings
    • Entering an employee’s compensation
    • Importing payroll data
    • Preparing the month’s payroll
    • Getting started with Payroll
  • Payroll outsourcing
    • SwissSalary connector: permissions in Business Central
  • Compliance & exports
    • Compensation types and payroll items
    • Approving payroll and exporting items
  • Swiss payroll
    • The Swissdec cockpit
    • Salary certificates, annual statements and payroll accounts
    • Calculating and closing monthly payrolls
    • Completing employee data
    • Setting up Swiss payroll
    • Getting started with Swiss payroll
  • Canadian payroll
    • Producing a record of employment
    • Preparing T4 and RL-1 slips
    • Tracking remittances to the CRA and Revenu Québec
    • Calculating, closing and publishing a Canadian pay
    • The employee’s Canadian payroll tab: tax forms and takeover
    • Setting up a Canadian employer and the payroll settings
    • Getting started with Canadian payroll
  • Moroccan payroll
    • Monthly statements and returns
    • Calculating, closing and publishing the month’s payroll
    • Preparing an employee’s Morocco payroll record
    • Setting up Morocco payroll
    • Getting started with Morocco payroll

Platform

57
  • Emails
    • Automated emails: catalogue and activation
    • Editing an email template
    • Sending reminders until the action is done
    • Tracking the sending history
  • Employee self-service
    • Finding your way around Illizeo: menu, search, language and personal settings
    • The dashboard: your home page
    • My profile: viewing and updating my information
    • The calendar and syncing your work calendar
    • Configuring the company dashboard
  • Flows & approvals
    • Workflows: from request to decision
    • Approving, rejecting or delegating a request
    • Monitoring workflow activity: overview and metrics
    • Creating and editing a workflow
    • Global settings, deadlines and automatic actions
    • HR processes: documents, signatures and deadlines
  • Alerts & notifications
    • The notification centre (the bell)
    • Choosing your notifications
    • Setting company notification defaults and locks
    • Publishing an announcement on the dashboard
    • Role reminders and personal reminders
  • Mobile app
    • Configuring the mobile app
  • Security & compliance
    • Password, session length and IP addresses
    • Two-factor authentication and open sessions
    • Single sign-on (SSO)
    • Country compliance and privacy consent statements (DPCS)
    • Data protection registers
    • Data backups
  • Permissions & roles
    • Understanding roles and permissions
    • Creating and managing roles
    • Setting permissions in the matrix
    • Defining a role’s target population
    • Assigning a role to employees
    • Creating employee groups
  • Governance & security
    • Governance and traceability: overview
    • Viewing user logs
    • The GDPR audit log
    • Running an access review
    • Separation of duties (SoD)
    • Finding the change history
  • REST API
    • Creating and managing API tokens
    • Monitoring and troubleshooting an API token
    • Public API: developer guide
    • The help desk API
  • Webhooks
    • Creating and managing a webhook
    • Monitoring deliveries and retries
    • Receiving and verifying a webhook
    • Webhook event catalogue
    • Help desk webhooks
  • SFTP exports
    • Setting up the company SFTP server
    • SFTP deposits and how to track them
  • Subscription & settings
    • Setting up organisation code generation
    • Finding your way around Settings
    • Installing modules and choosing who can use them
    • Subscribing and changing your subscription
    • Invoices, payment, usage and workspace ownership
    • Workspace logos and global settings
    • Giving Illizeo Support access

Consulting

1
  • Deployment support
    • The Illizeo Pulse method: how we deploy your HRIS

Attendance & Badging

11
  • Filling in your timesheet from your Outlook calendar
  • Attendance & badge clocks: module overview
  • Clocking in and out
  • Filling in and submitting your timesheet
  • Approving attendance and following the team
  • Creating and assigning attendance profiles
  • Clocking rules, entry closing and presence reasons
  • Hour counters
  • Allowances and on-call
  • Badge clocks
  • Administering the Attendance module: permissions, notifications, import/export and personal data

Absence Management

8
  • Absence management: overview and vocabulary
  • Requesting, editing and cancelling an absence
  • Leave balances and counters
  • Approving absence requests
  • The absence calendar
  • Configuring absence types and their policies
  • Company rules and public holidays
  • Administering the Absence management module

Expense Reports

7
  • Expenses: overview and life of an expense report
  • Entering, submitting and tracking an expense
  • Declaring mileage and per diem
  • Approving expense reports
  • Reimbursing, analysing and accounting for expenses
  • Configuring the Expenses module
  • Administering the Expenses module: permissions, notifications, personal data and FAQ

Performance & Goals

13
  • Performance: overview and navigation
  • Setting and tracking objectives (OKRs)
  • Objective-based bonus: preparing and sending to payroll
  • Scheduling and tracking 1:1 meetings
  • Designing review forms
  • Setting up a review cycle and campaign
  • Launching, tracking and closing a campaign
  • Completing and approving reviews
  • The end-of-cycle dossier: validating and signing
  • Continuous feedback
  • The talent review (9-box)
  • Tracking professional interviews (France)
  • Administering the Performance module

Surveys & Engagement

6
  • Survey settings
  • Reading results and generating reports
  • Tracking responses and sending reminders
  • Answering a survey
  • Creating and launching a survey
  • Getting started with Surveys

FlexOffice

18
  • Flex Office: module overview
  • Flex Office calendar
  • Flex Office: week template
  • Flex Office: parking
  • Flex Office: meals
  • Flex Office: visitors
  • Flex Office: meeting rooms
  • Flex Office: site events
  • Flex Office: approvals
  • Flex Office: schedule reminders
  • Flex Office: dashboard
  • Flex Office: locations and floor plans
  • Flex Office: attendance profiles
  • Flex Office: general settings
  • Flex Office settings
  • Flex Office: imports
  • Flex Office: notifications
  • Flex Office: integrations

HR requests

5
  • Administering the HR requests module: traceability, personal data, languages and FAQ
  • Configuring the HR requests module
  • Handling HR requests (HR team)
  • Submitting and tracking an HR request
  • HR requests: overview and life of a request

Scheduling

7
  • Getting started with Scheduling
  • Creating and publishing a schedule
  • Open shifts and replacements
  • Availability and preferences
  • Clocking in on a shift and geofencing
  • Scheduling settings
  • Scheduling public API and webhooks

Budget & payroll costs

10
  • Budget & payroll costs: module overview
  • Monitoring payroll costs against the budget
  • Running the salary review
  • Pay scales and contract positioning
  • Analysing pay equity (Gender Equality Act)
  • Simulating payroll costs and planning headcount
  • Fiscal years, funding and coverage rate
  • Budget module indicators, exports and action log
  • Administering the Budget & payroll costs module: settings, approval workflows and permissions
  • Administering the Budget & payroll costs module: notifications, traceability, personal data and glossary

BDESE

9
  • Recurring works council consultations
  • The works council area: staff list, mandates and experts
  • Calculating and publishing the gender equality index
  • BDESE payroll data
  • Entering, validating and publishing data
  • BDESE settings
  • The group view
  • Choosing a BDESE’s structure and designating contributors
  • Declaring and managing BDESE databases

Training

12
  • Training: overview and navigation
  • Your training space: home, path, catalogue and certificates
  • Taking an online course: lessons, quizzes and assignments
  • Requesting training and getting it approved
  • Building and publishing a course in the catalogue
  • Scheduling sessions and taking attendance
  • The trainer workspace: preparing, running and declaring your hours
  • Steering training: annual plan, budget and analytics
  • Tracking certifications and renewals
  • Managing skills: framework, matrix and gaps
  • Agreements, invoices, certificates and regulatory filings
  • Administering the Training module

Employee referrals

5
  • Setting up the referral programme and campaigns
  • Managing referrals and approving the bonus
  • Tracking your referrals, badges and the ranking
  • Referring a candidate or sharing your link
  • Getting started with Referrals

Whistleblowing

6
  • Analytics, export and data privacy
  • Configuring the scheme
  • Handling a whistleblowing case
  • Submitting and tracking a report
  • Setting up channels and naming handlers
  • Getting started with whistleblowing

CRM

26
  • Enabling and administering the CRM module
  • Managing accounts
  • Managing contacts
  • Finding duplicates and merging records
  • Activities and “My activities”
  • Tracking opportunities in the pipeline
  • The catalogue and quotes
  • Importing, exporting and using the API
  • The dashboard and sales targets
  • CRM settings
  • Protecting contact data (GDPR)
  • From a won deal to a project
  • CRM webhooks
  • Connecting the CRM to Power Automate
  • Connecting the CRM to n8n
  • Microsoft 365 in the CRM: emails, meetings and Teams
  • The CRM forwarding address
  • Artificial intelligence in the CRM
  • Getting records and sendings approved
  • Sales commissions
  • The CRM and HR: time, expenses, absences and departures
  • The CRM in the mobile app
  • Links between organisations and multi-organisation projects
  • Follow-up pipelines: support and business set-up files
  • Memberships and dues
  • Events and public registrations

Help desk

20
  • Setting up the help desk
  • Submitting and following a help desk request
  • Handling help desk tickets
  • Help desk service commitments
  • External portal and incoming e-mail
  • The knowledge base
  • Help desk satisfaction and reporting
  • Workflows and ticket approval
  • The help desk and the CRM: linked customers and contracts
  • Client organisations: shared portal, contact persons and directory
  • The help widget on your customer’s website
  • The help desk in Microsoft Teams
  • Your brand on the portal and e-mails
  • Merging duplicates, linking tickets, observers and copies
  • Help desk automations: rules and macros
  • The help desk API
  • Help desk webhooks
  • The service catalogue: one request, several teams
  • Major incidents and problems
  • Administering the help desk
View Categories
  • Accueil
  • Centre d'aide
  • Help desk
  • The help desk API

The help desk API

Wilfrid Paul Robert Dusseaux
Updated on 20.11.2026

12 mins de lecture

0:00 / 13:26
  • View as Markdown Open this page as plain Markdown (opens in a new tab)
  • Open in ChatGPT Ask questions about this page (opens in a new tab)
  • Open in Claude Ask questions about this page (opens in a new tab)
  • Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)

Your tools — monitoring, website, ERP, n8n, Power Automate — can work directly in the help desk: file a ticket when an alert fires, find it again, reply on the team’s side or on behalf of the requester, change its status and priority, write an internal note and read the published articles of the knowledge base. This article describes that part of Illizeo’s public API. It is for the developers who build the integration and for the help desk administrator who authorises it.

Before you start #

  • The help desk module must be installed, and your subscription must include API access.
  • The help desk administrator opens the services concerned to the API (see below): a token never reaches a closed service.
  • The token is created under Settings › Manage Illizeo › API Tokens (see Creating and managing API tokens). It acts on behalf of the person who creates it: that person must hold, in the role matrix, Help center agent or Administer the help center, at the Access level to read and the Execute level to write, and the module must be open to them.
  • The API address, authentication, response envelope and rate limits are common to the whole API: see Public API: developer guide.

Opening a service to the API #

Every service is closed to the API by default. Opening it requires the Administer the help center right at the Execute level.

  1. Open Settings › Help center › Services and click the service.
  2. In the Identity section, under Public API, switch the toggle to Open to the API.
  3. Click Save.
Identity section of a service: Open to, State, then Public API with the Open to the API toggle, the sentence API tokens and webhooks only reach the services opened here, and the Save button
Opening a service to the API

As the screen reminds you, API tokens and webhooks only reach the services opened here. Closing a service again applies from the next call: its tickets and articles then answer 404, and it no longer sends webhooks. Opening and closing are recorded in the activity log.

Creating the integration’s token #

Under Settings › Manage Illizeo › API Tokens, click New token. Choose the Name with care: it signs what the integration writes. A token named “Supervision” replies under the “via API · Supervision” mark on the ticket page, and the e-mail the requester receives is signed “Supervision”. Then, in the Data group, tick the help desk scopes the integration needs:

Scope (screen) Code What it opens
Help center — tickets (Read) helpdesk_tickets:read List services and tickets; read a ticket, its public messages and its public timeline.
Help center — tickets (Write) helpdesk_tickets:write File a ticket, reply (on the team’s or the requester’s side), change the status and priority.
Help center — internal notes (Read) helpdesk_notes:read Read internal notes, on their own or with the ticket.
Help center — internal notes (Write) helpdesk_notes:write Write an internal note.
Help center — knowledge base articles (Read) helpdesk_articles:read List and read published articles.
Help center — webhook subscriptions (Write) helpdesk_webhooks:write Subscribe to the help desk webhooks and unsubscribe (see Help desk webhooks).
New API token form, Data group: Help center — tickets ticked for read and write, internal notes unticked, knowledge base articles ticked for read, webhook subscriptions unticked
The help desk scopes of a token

Write does not include read: an integration that files tickets and then follows them ticks both. Without a helpdesk_notes scope, no internal note goes out or comes in through the API. These scopes only appear if the help desk module is enabled.

What the token reaches #

The token reaches the services open to the API, and among them those its creator reaches in Illizeo:

  • created by an agent: the services they are an agent of. The token acts there as on screen: on an unassigned ticket, on the agent’s own tickets, and on all the tickets of a service they manage. A colleague’s ticket can be read, given a note or written to on behalf of the requester; replying on the team’s side or changing its status or priority is refused (422);
  • created by the help desk administrator (“Administer the help center” at the Execute level): every service open to the API, with the right to act on every ticket.

A ticket or article outside this reach answers 404, as if it did not exist. If the creator’s rights change, the token’s follow from the next call.

The operations #

All addresses start from https://api.illizeo.app, with the Authorization: Bearer illz_… header. In the addresses, {ticket} is a ticket’s number (AST-000812) or its identifier, and {article} an article’s slug or its identifier.

Operation Scope Use
GET /v1/helpdesk/services helpdesk_tickets:read The services reached, with their request types and the fields of their form.
GET /v1/helpdesk/tickets helpdesk_tickets:read The list of tickets, without their messages.
GET /v1/helpdesk/tickets/{ticket} helpdesk_tickets:read A ticket, its messages and its public timeline.
POST /v1/helpdesk/tickets helpdesk_tickets:write File a ticket.
PATCH /v1/helpdesk/tickets/{ticket} helpdesk_tickets:write Change the status or the priority.
POST /v1/helpdesk/tickets/{ticket}/messages helpdesk_tickets:write Reply, on the team’s side or the requester’s side.
GET /v1/helpdesk/tickets/{ticket}/notes helpdesk_notes:read The ticket’s internal notes.
POST /v1/helpdesk/tickets/{ticket}/notes helpdesk_notes:write Write an internal note.
GET /v1/helpdesk/articles helpdesk_articles:read Search the published articles.
GET /v1/helpdesk/articles/{article} helpdesk_articles:read Read a published article.
POST /v1/helpdesk/webhooks, DELETE /v1/helpdesk/webhooks/{id} helpdesk_webhooks:write Subscribe to the help desk webhooks, unsubscribe.

The Documentation button of the tokens page describes each operation in the Help center card; its openapi.json button gives the full contract.

API documentation in the application, Help center card: its introduction then the twelve operations, each with its method, its address under /v1/helpdesk, its summary and its scope
The help desk operations in the API documentation

Reading tickets #

The list accepts the filters statut (one or more codes separated by commas), service_id, reference_externe and modified_since (an ISO 8601 date; modifie_depuis is accepted too). A ticket counts as modified when its record changes or when activity visible to the token is added to it: a message, a status change. Tickets come by ascending identifier, 50 per page (limit, 200 at most); the response carries items, next_cursor and has_more. To synchronise another system, read again with cursor set to next_cursor as long as has_more is true.

A ticket carries in particular numero, objet, description, statut, priorite, service, type, canal, demandeur (salarie or externe, with name and e-mail), agent, its dates (depose_le, modifie_le, resolu_le, clos_le, in ISO 8601 UTC), its first-response and resolution echeances, the reponses_au_formulaire, the reference_externe, and the numbers of the parent (the request it is a task of) and of the major incident it is attached to, or null. Keys are in French, as in the application; values are codes:

Field Codes (label on screen)
statut new (New), taken (In progress), waiting_requester (Waiting for the requester), waiting_third_party (Waiting for a third party), resolved (Resolved), closed (Closed)
priorite low (Low), normal (Normal), high (High), critical (Critical)
canal internal (Employee space), portal (Portal), email (E-mail), agent (Filed by an agent), widget (Website widget), teams (Microsoft Teams), api (API)

Reading a ticket adds messages — each with cote (equipe, demandeur or note), auteur, via_api, le, corps in HTML and pieces (name and size; the files are downloaded in Illizeo) — then chronologie, the timeline the requester sees. Internal notes only appear there with the helpdesk_notes:read scope.

Filing a ticket #

The body of POST /v1/helpdesk/tickets carries service_id and objet (required), if needed type_id, description, priorite, reponses_au_formulaire and reference_externe (your own identifier, for example the alert’s), and the demandeur: email (required), nom and langue.

POST /v1/helpdesk/tickets
Authorization: Bearer illz_…
Content-Type: application/json

{
  "service_id": 3,
  "objet": "File server unreachable",
  "description": "FS-01 has not responded since 08:42.",
  "priorite": "high",
  "demandeur": { "email": "supervision@your-company.co.uk", "nom": "Supervision", "langue": "en" },
  "reference_externe": "ALERT-20261120-0042"
}

The response, a 201, returns the ticket and its thread ("numero": "AST-000812", "statut": "new", "canal": "api"…). The ticket enters the queue like any other: help desk rules, service commitments, acknowledgement to the requester.

  • The requester is given by their e-mail address. If the service is open to employees and the address belongs to a single active employee who may file requests (“Help center requests” right at the Execute level), it is that employee. Otherwise, if the service is open to external people, it is an external person, created on their first request in the langue given. Otherwise, the response is 422. An alert can therefore carry the address of the tool that raises it.
  • The type is optional. If given, it must be active and offered to this requester, and its required fields must appear in reponses_au_formulaire, under the keys returned by GET /v1/helpdesk/services.
  • The priority, if omitted, is the type’s, otherwise Normal; it is raised to the minimum set by the client organisation’s contract, if there is one.
  • A service closed to the API, outside the token’s reach or inactive is refused (422 on service_id).

Replying #

POST /v1/helpdesk/tickets/{ticket}/messages takes a corps in HTML, cleaned on arrival, and a cote.

  • "cote": "equipe": a public reply from the team, marked “via API ·” followed by the token’s name, and sent to the requester in an e-mail signed with that name. It counts as the first response for service commitments, but does not take the ticket: it keeps its agent, or still has none. An optional statut changes it in the same move; the requester then receives a single e-mail. The reply is refused (422) on a closed ticket, on a ticket awaiting approval and on a colleague’s ticket. On a task of a catalogue request, it is written on the request, as on screen.
  • "cote": "demandeur": the reply is written on behalf of the ticket’s requester, for example from your customer portal. It follows the rules of a requester’s reply: a ticket waiting for the requester goes back to In progress; a ticket resolved within the reopening delay is reopened; after that delay, or on a closed ticket, a follow-up is created and receives the message. statut is not accepted on this side, nor a reply on a task.
POST /v1/helpdesk/tickets/AST-000812/messages
{ "cote": "equipe", "corps": "<p>The probe is back to normal.</p>", "statut": "resolved" }

The response, a 201, carries message (the message written, with "via_api": true) and ticket, the ticket that received it: the same one, its follow-up, or the request of a task.

Agent’s page of ticket AST-000071: API channel, no agent, then the conversation: automatic reply, team reply marked via API · Supervision, an agent’s internal note, requester’s reply written through the API
A ticket filed and followed through the API, as the agent sees it

On the ticket page, agents see the API channel and the via API · Supervision mark on each of the integration’s messages; the timeline names it too (“Supervision (API) replied”). The requester sees the same mark in their request.

Changing the status or the priority #

PATCH /v1/helpdesk/tickets/{ticket} takes statut, priorite or both, all or nothing. The rules are those of the screen:

  • a closed ticket no longer changes; a resolved ticket can only go back to In progress or be closed; a ticket only becomes New again from In progress;
  • a ticket awaiting approval changes neither status nor priority; the status does not change on a ticket attached to an open major incident, and a catalogue request is neither resolved nor closed while one of its tasks is open (422, with the reason);
  • the priority no longer changes on a resolved or closed ticket, and does not go below the minimum of the client organisation’s contract;
  • a colleague’s ticket is refused (422).

The response, a 200, returns the ticket without its thread. In a single call, the priority is handled before the status: to reopen a resolved ticket and change its priority, make two calls, status first. The change is signed with the token’s name in the timeline. "statut": "taken" gives the ticket to nobody, and "statut": "new" returns it to the queue, without an agent.

Internal notes #

With helpdesk_notes:write, POST /v1/helpdesk/tickets/{ticket}/notes and a corps in HTML write an internal note signed with the token’s name, on any ticket reached, even closed, awaiting approval or held by a colleague. It changes neither the status nor the agent, and is never shown to the requester. With helpdesk_notes:read, GET …/notes returns the notes alone, and reading a ticket mixes them with its messages ("cote": "note").

Knowledge base articles #

With helpdesk_articles:read, the integration reads the published articles of the services reached, in their current version, for example to suggest answers on your website. GET /v1/helpdesk/articles accepts q (the same search as the space’s help), service_id, public (interne or externe; internal and external are accepted too) and langue, and returns for each article its title, an excerpt, the language served, its visibility and its category. GET /v1/helpdesk/articles/{article} returns the whole article, body in HTML; repli is true when the language requested is missing and another one is served. A draft, an archived article or one outside the token’s reach answers 404, and an article attached to no service is not served. See The knowledge base.

Refusals #

Response Cause
403, SCOPE_MANQUANT The operation’s scope is not ticked on the token; data.required_scope names it. A read-only token cannot write anything.
403, MODULE_NOT_ACTIVE or MODULE_DISABLED_FOR_EMPLOYEE (code field) The help desk is not enabled in the space, or not open to the token’s creator.
403 The token’s creator does not hold the screen right at the right level: “Help center agent” or “Administer the help center” (the latter, at the Execute level, for webhooks).
404, NOT_FOUND Ticket or article outside the token’s reach, or in a service closed to the API.
422, VALIDATION_ERROR A field refused, detailed in errors; or a screen rule, whose reason is in message, in the language requested by X-Locale or Accept-Language, otherwise in the token creator’s language.

Good to know #

  • API actions are signed by no person: the token’s name signs them in the thread and the timeline. That name is copied onto each message: renaming the token does not change messages already written. In the activity log, changes are recorded under the token creator’s name.
  • A team reply written through the API on an agent’s ticket does not send them a notification.
  • Attachments cannot be sent through the API: messages only name them.
  • Each call counts as one unit in the API platform usage, as does each webhook delivered (see Monitoring and troubleshooting an API token).
  • The API channel appears in reporting and in the “Channel” condition of automations.
  • To be told what happens to tickets rather than reading them again, subscribe to their webhooks: see Help desk webhooks.

Similaire #

Updated on 20.11.2026
Help desk automations: rules and macrosHelp desk webhooks
Table des matières
  • Before you start
  • Opening a service to the API
  • Creating the integration’s token
  • What the token reaches
  • The operations
  • Reading tickets
  • Filing a ticket
  • Replying
  • Changing the status or the priority
  • Internal notes
  • Knowledge base articles
  • Refusals
  • Good to know
Onboarding✦Offboarding✦Crossboarding✦Reboarding✦Referrals✦Equipment✦AI✦Signatures✦NPS✦Attendance✦Badging✦Leave✦Performance✦Objectives✦Surveys✦Engagement✦Time✦Roles✦Permissions✦Flows✦Approvals✦Salaries✦Expenses✦FlexOffice✦Projects✦
Onboarding✦Offboarding✦Crossboarding✦Reboarding✦Referrals✦Equipment✦AI✦Signatures✦NPS✦Attendance✦Badging✦Leave✦Performance✦Objectives✦Surveys✦Engagement✦Time✦Roles✦Permissions✦Flows✦Approvals✦Salaries✦Expenses✦FlexOffice✦Projects✦
International HR platform

Run HR
in minutes,
not in days.

Try for free Book a demo
illizeo

Onboarding, payroll, leave, talent — one engine for your teams.

SWISS MADE
Features
  • Solutions
  • Pricing
About
  • Careers
  • Press
  • Customers
  • Partner portal
  • Contact
Resources
  • Blog
  • Global family allowances
  • Comparisons
  • Help Center
  • FAQ
  • Security
Contact
+41 78 669 05 65 contact@illizeo.com
Newsletter
1 email a month. Useful only.
Coming soon to App Store Coming soon to Google Play
All systems operational · Swiss hosting · GDPR & nFADP
© 2026 Illizeo Cloud Solutions
FR/EN
Privacy Policy Legal Notice & Terms Illizeo Terms AI Terms Cookie Settings Sub-Processors MTO Data Processing Addendum (DPA) Support Services Terms
illizeo-logo-primary-white
Gérer le consentement

Afin de vous offrir la meilleure expérience possible, nous utilisons des technologies telles que les cookies pour stocker et/ou accéder aux informations relatives à votre appareil. En acceptant ces technologies, vous nous autorisez à traiter des données telles que votre comportement de navigation ou vos identifiants uniques sur ce site. Le refus ou le retrait de votre consentement peut avoir un impact négatif sur certaines fonctionnalités et fonctions.

Fonctionnel Always active
Le stockage technique ou l'accès est strictement nécessaire à des fins légitimes afin de permettre l'utilisation d'un service spécifique explicitement demandé par l'abonné ou l'utilisateur, ou dans le seul but d'effectuer la transmission d'une communication sur un réseau de communications électroniques.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistiques
Le stockage technique ou l'accès utilisé exclusivement à des fins statistiques. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
Le stockage technique ou l'accès est nécessaire pour créer des profils d'utilisateurs afin d'envoyer des publicités ou de suivre l'utilisateur sur un site web ou sur plusieurs sites web à des fins marketing similaires.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Afficher les préférences
  • {title}
  • {title}
  • {title}