Okapi Okapi

BigCommerce API GET /stores/{id}/v3/hooks/events endpoint removal

Deprecated, no dateSubscribe to BigCommerce APIShare

BigCommerce deprecated the GET /stores/{id}/v3/hooks/events endpoint without a shutdown date. Calls to this endpoint will eventually fail once it is removed. The change affects integrations querying the Get Events endpoint for webhook event data.


Calls it hits

  • GET /stores/{id}/v3/hooks/events

What to use instead of these calls

Subscribe to webhook delivery exception hooks, which supersede the Get Events endpoint.

In BigCommerce API's words

Deprecated the Get Events endpoint.

BigCommerce API, Announcement

Facts

API
BigCommerce API api.bigcommerce.com
Kind
Endpoint removal
Announced
May 4, 2023
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against BigCommerce API's own pages

Questions

When does this change take effect?

BigCommerce API deprecated GET /stores/{id}/v3/hooks/events without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: BigCommerce 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 BigCommerce API 1

  1. No date /stores/{id}/v2/pages*Removal Deprecated, no date

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

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

1What to follow

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