Integrations: API, webhooks and MCP
Your ticketing tool, your monitoring platform or your AI assistant can talk to ChargeTeam: create a request, follow the call-out, fetch the report. Here is what exists, and what has already been proven.
API
The API creates a call-out request with your own ticket number, reads your register of sites and chargers, your call-outs and your reports, and receives charger statuses sent by your monitoring platform. Every request is reviewed by our team before it is assigned.
Its machine-readable description is published in OpenAPI 3.1 format, ready to import into your tools.
Keys with limited scopes
An administrator of your company creates keys in your client area; each key is shown only once. You choose its scopes (reading or writing requests, reports, call-outs, events) and, if you wish, a daily quota.
A key can be rotated: the new one keeps the same scopes and the old one stays valid for 24 hours. Every call is recorded in a log visible for 90 days; request contents are not kept.
Signed webhooks
Each step of a call-out can be sent to your address: request received, call-out scheduled, technician on site, call-out completed, sign-off signed, report approved, cancellation. Each delivery is signed (HMAC-SHA256); without a response it is retried for about four hours, then can still be resent from the log.
Events go out in regular batches, every five minutes. The signing secret can be rotated and is encrypted at rest. No amounts and no personal data about technicians are sent.
Exports
Requests, call-outs, tickets and reports can be exported as CSV or JSON, from your client area or through the API. Column names are stable: we add columns, we never remove them.
Ticketing connectors
Connectors exist for Zendesk, Jira Service Management, ServiceNow, Freshdesk, Salesforce Service Cloud, Sitetracker, HubSpot Service Hub and Microsoft Dynamics 365. They have only been tested against simulated servers: they are available on request, and each one is validated with your own instance when it goes live, on a test ticket.
For any other tool, including Zapier, Make or n8n, the generic API and webhook are enough.
AI assistants (MCP)
Your AI assistant (Claude, ChatGPT or any client compatible with the Model Context Protocol) can connect to your client area with your ChargeTeam account. By default it can only read: sites and chargers, requests, call-outs and reports. It never sees amounts, internal notes or any data about technicians.
If you allow it separately, it can prepare a request: it stays a draft until you confirm it yourself in your client area, and then our team reviews it.
Our automated tests cover authorisation and the tools. The end-to-end connection from Claude and ChatGPT has not yet been proven: if you try it, tell us what you find.
Access under your control
Keys and assistant access are tied to your company, can be revoked at any time from your client area, and every call is logged.
Page written by ChargeTeam, last updated on October 3, 2026.
An integration project?
Describe your tool and what you need: we tell you what already plugs in.