Okapi Okapi

Auth0 API enabled_clients body parameter removal on PATCH /api/v2/connections/{id}

Stopped workingSubscribe to Auth0 APIShare

On July 13, 2026, the body parameter enabled_clients on PATCH /api/v2/connections/{id} was removed. Calls including this parameter fail since that day.


Calls it hits

  • PATCH /api/v2/connections/{id}
  • body parameter enabled_clients

What to use instead of these calls

Update the clients enabled on a connection with PATCH /api/v2/connections/{id}/clients, and read them with GET /api/v2/connections/{id}/clients.

In Auth0 API's words

The enabled_clients field, within the Management API connection object, is deprecated in the following scenarios:

Auth0 API, Announcement

Facts

API
Auth0 API *.auth0.com
Kind
Parameter removal
Announced
January 13, 2026
Takes effect
July 13, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Auth0 API's own pages

Questions

When does this change take effect?

Calls to PATCH /api/v2/connections/{id}, body parameter enabled_clients on Auth0 API stopped working on July 13, 2026.

What happens to calls after July 13, 2026?

They have failed since July 13, 2026.

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 Auth0 API 2

  1. /api/v2/hooks*Removal Stops workingin 12 days
  2. /api/v2/rules*Removal Stops workingin 12 days

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to Auth0 API

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

1What to follow

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