Evernex Connect API
Get Your Access Token
This API is secured with OAuth 2.0 (Client Credentials grant). See Get Access Token to exchange your client ID and secret for an access token - every other operation on this API requires it in the Authorization: Bearer <access_token> header.
The Evernex Connect API lets you raise support cases, follow their progress and exchange information with our support teams directly from your own tools, without going through e-mail or a web portal.
What you can do
Create a support case for a piece of equipment covered by one of your contracts, attach files to it, follow the status of the intervention, exchange messages with the engineers handling it, and update the details of a case while it is still open.
Authentication
Every request must carry a bearer token obtained with the credentials issued to you. Tokens are short-lived: request a new one when yours expires rather than at every call. See the security section below for the token endpoint, the required parameters, and what a request refused for a missing or expired token looks like, since those answers do not follow the error format described here.
Cases you can see
A request only ever returns cases belonging to the account tied to your credentials. There is no way to reach another customer's cases, and a case number that exists but is not yours is reported as not found.
Lists and pagination
The two list endpoints return a page of results together with the counters needed to walk through
the whole set: total is the number of matching records ignoring pagination, and count is the
number returned in this page. Compare offset + count with total to know whether another page
is waiting. Records are ordered from the most recent to the oldest.
Dates
Every date and time is expressed in UTC, in the standard YYYY-MM-DDThh:mm:ssZ form. Dates you
send are interpreted the same way; for a requested intervention date, the time zone of the site
where the equipment sits is applied on our side.
When something goes wrong
Errors carry a code you can rely on and a readable explanation of what to correct, and use the
usual status codes: 400 when the request is malformed or a value is out of range, 404 when the
case does not exist or does not belong to you, 409 when the case is closed and no longer accepts
changes, and 500 when the failure is on our side and worth reporting to us.
A request carrying no token, or a token that is malformed or expired, is refused before it reaches
the API and also answered with a 400, but in a simpler form that does not follow the format
above. The security section describes it, and it is worth handling separately: a 400 does not
always mean your request was wrong.
Rate Limiting
Requests are limited per client to 300 requests per minute and 50,000 requests per day. Requests beyond either limit are rejected with a 429 status - space out or batch your calls if you expect to approach them. These limits are enforced at the API gateway and are not part of the error format described above.