Okapi Okapi

Gorgias API GET /api/tickets/{id}/messages endpoint removal

Deprecated, no dateSubscribe to Gorgias APIShare

Gorgias API has deprecated GET /api/tickets/{id}/messages without announcing a shutdown date. Calls made to this endpoint will eventually fail. Review any integrations relying on this path to prepare for its removal.


Calls it hits

  • GET /api/tickets/{id}/messages

What to use instead of these calls

Use List messages, GET /api/messages?ticket_id={ticket_id} instead.

In Gorgias API's words

This endpoint has been deprecated.

Gorgias API, Announcement

Facts

API
Gorgias API *.gorgias.com
Kind
Endpoint removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Gorgias API's own pages

Questions

When does this change take effect?

Gorgias API deprecated GET /api/tickets/{id}/messages without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Gorgias API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from Gorgias API 2

  1. PUT /api/tickets/searchEndpoint removal Stopped working
  2. POST /api/stats/self-service-overviewEndpoint removal Stopped working

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub

Get notifications

Subscribe to Gorgias API

Hear about each breaking change Gorgias API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Gorgias API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.