v2

Released 2018-03-14Active

Migration Effort

Medium

Estimated Hours

~8h

Primary risk if skipped: API requests failing due to incorrect identifier usage, leading to service disruptions.

Breaking Changes2

endpointHighCore API

/api/v2/tickets/{ticket_id}.json

The `/api/v2/tickets/{ticket_id}.json` endpoint no longer supports retrieving tickets by their `id` directly. Instead, it now requires the `external_id` for retrieval.

Before

GET /api/v2/tickets/{ticket_id}.json

After

GET /api/v2/tickets.json?external_id={external_id}

→

Update all calls to this endpoint to use the `external_id` parameter instead of the ticket ID.

endpointHighCore API

/api/v2/users/{user_id}.json

Similar to tickets, the `/api/v2/users/{user_id}.json` endpoint has been changed to require `external_id` instead of the user's internal `id` for fetching a user.

Before

GET /api/v2/users/{user_id}.json

After

GET /api/v2/users.json?external_id={external_id}

→

Modify API calls to use the `external_id` parameter when retrieving users.

Never get blindsided by an API change again

Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.

Join the Waitlist