canonical: https://jentic.com/apis/gestion-diagnostic.fr/gestiondiag

# Gestion Diagnostic Fr GestionDiag API

The GestionDiag API runs a field-service back office for diagnostic businesses, organising client records, appointment dossiers, and the technicians who carry out the work. It creates, lists, duplicates, and archives dossiers, manages appointment dates and callback requests, and keeps client profiles and contacts up to date. It also manages technicians with their calendar access and certifications, uploads and retrieves diagnostic reports against a dossier, and tags dossiers and files. User requests authenticate with a JWT bearer token from the login endpoint, and some dossier endpoints also accept a security token as a query parameter.

## For AI agents

Manage diagnostic client records, appointment dossiers, technicians, and uploaded reports for a field-service business. Authenticates with a JWT bearer token, with an optional query security token on some dossier endpoints.

## Scope

Does not handle invoicing, payments, or the diagnostic measurements themselves. Use for managing diagnostic client records, appointment dossiers, technicians, and reports only.

## Capabilities

- Create, list, duplicate, and archive diagnostic appointment dossiers
- Manage appointment dates and raise callback requests for a dossier
- Keep client records and their contacts up to date
- Manage technicians along with their calendar access and certifications
- Upload, retrieve, and delete diagnostic reports against a dossier
- Tag dossiers and files and manage the tag list
- Email the assigned technician and mark a dossier read or unread

## Use cases

### Agent-Driven Dossier Intake

An AI agent connected through Jentic can open and route diagnostic jobs without a developer wiring the login token exchange. The agent creates a client record if needed, opens a dossier, sets the appointment date, and emails the assigned technician. Jentic injects the bearer token at call time so the credential never reaches the agent.

Example prompt: Create a client record, open a dossier for them, set its appointment date, and email the assigned technician

### Report Collection and Delivery

Once a technician finishes a visit, the report needs attaching to the right dossier. The agent uploads the diagnostic report against the dossier id, retrieves the stored reports to confirm, and tags the file. This keeps each dossier's paperwork complete and findable.

Example prompt: Upload a diagnostic report to a dossier, retrieve the dossier's reports to confirm, and tag the uploaded file

### Technician and Scheduling Admin

Operations teams keep the technician roster and appointments current. The agent lists technicians, checks a technician's certifications and calendar access, and updates the appointment date on a dossier accordingly. This keeps qualified technicians matched to the right jobs.

Example prompt: List technicians, read a technician's certifications, then set a dossier's appointment date for that technician

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/rendez-vous/liste` | List dossiers |
| POST | `/rendez-vous/` | Create a new dossier |
| PUT | `/rendez-vous/gestion-rdv` | Set or change the appointment date |
| GET | `/rendez-vous/{id}` | Get a dossier by id |
| POST | `/compte_client/ajout` | Create a client record |
| POST | `/techniciens/ajout` | Create a technician |
| POST | `/upload/{rdv_id}` | Upload a report to a dossier |

## Key resources

- **Dossiers** — Create, list, read, duplicate, archive, and manage appointment dates on dossiers
- **Clients** — Create, list, update, and delete client records and manage contacts
- **Techniciens** — Manage technicians, their calendar access, and certifications
- **Rapports** — Upload, retrieve, and delete reports against a dossier
- **Tags** — Create and manage tags and attach them to dossiers and files

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 56 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 55 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 45 / 100
  - AI Discoverability: 68 / 100
- **View full report:** https://jentic.com/apis/gestion-diagnostic.fr/gestiondiag/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring GestionDiag by hand means posting the user mail and password to the login endpoint for a JWT bearer token, refreshing it on a 401, and remembering which dossier endpoints also take a query security token, all yourself. Through Jentic you install once, import GestionDiag from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** GestionDiag puts the dossier, client, and technician ids in the URL path, for example `/rendez-vous/{id}` and `/compte_client/{Client_ID}`, so a rule can pin your agent to reading individual records. You choose which operations it may call, so destructive ones like archiving a dossier or deleting a client, technician, or report are not included unless you add them.
- **Credential handling:** Your GestionDiag bearer token and security token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a diagnostic dossier' or 'set an appointment date', and Jentic returns the matching GestionDiag operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Zoho FSM** — Field service management for work orders, appointments, and technicians
- **Acuity Scheduling** — Appointment booking and calendar management
- **Calendly** — Let clients self-book available appointment slots
- **Zoho CRM** — CRM for the client records behind dossiers

## FAQ

### What authentication does the GestionDiag API use?

Per its OpenAPI spec, the GestionDiag API uses a JWT bearer token obtained from the login endpoint and sent in the Authorization header. Some dossier endpoints also accept a security token passed as a query parameter for secured access. Through Jentic both credentials are stored encrypted by your own instance and injected at call time, so they never reach the agent.

### Is there a GestionDiag MCP server?

You don't need an MCP server to give your agent GestionDiag. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like creating a dossier or uploading a report on demand, without loading another server's tool definitions into its context.

### Can I limit what my agent is allowed to do with GestionDiag?

Yes. Write a rule that allows only the dossier read and report-upload operations under the records you choose, so the agent can intake jobs and attach reports but cannot archive a dossier or delete a client, technician, or report unless you add those operations, and every call it makes is logged. This matches an intake bot that opens jobs without destructive power.

### Can I schedule appointment dates with the GestionDiag API?

Yes. Use the appointment-date operation to set or change the date on a dossier, and raise a callback request when a client needs rescheduling. You can read a technician's calendar access to match the visit to an available technician.

### What are the rate limits for the GestionDiag API?

The OpenAPI spec does not specify rate limits. Check the GestionDiag documentation on SwaggerHub at https://app.swaggerhub.com/apis/CONTACT_125/gestiondiag-api-rendez-vous for current limits before running bulk dossier jobs.

### How do I open a diagnostic dossier with the GestionDiag API through Jentic?

Search Jentic for 'create a diagnostic dossier', which returns the client and dossier operations with their input schemas. The agent creates the client record, opens the dossier, sets its appointment date, and emails the technician, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.