Okapi Okapi

Freshdesk API GET /api/v2/email_configs* endpoint removal

Deprecated, no dateSubscribe to Freshdesk APIShare

Freshdesk API deprecated the GET /api/v2/email_configs* endpoints without a shutdown date. These old email configuration APIs are no longer supported, and affected calls fail.


Calls it hits

  • GET /api/v2/email_configs*

What to use instead of these calls

Read mailboxes with the Email Mailboxes API (GET /api/v2/email/mailboxes) instead.

In Freshdesk API's words

This section is for the old email configuration APIs which are no longer supported. You can find the new mailbox APIs which have additional capabilities here.

Freshdesk API, Announcement

Facts

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

Questions

When does this change take effect?

Freshdesk API deprecated GET /api/v2/email_configs* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Freshdesk 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.


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 Freshdesk API

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

1What to follow

Provider
  • Freshdesk 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.