I can’t offer any solutions for this right now other than just handling 409 status codes in response while creating clients. I’ll let others to chime in if anyone has solved this by other means. I wouldn’t recommend polling GET /clients endpoint to get all existing clients list and checking for uniqueness. By doing that you would be using your management api rate limit quota and management api endpoints are not supposed to be use fo high frequency calls, just for CI/CD or general CRUD configurations stuff.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Can't trigger 409 when creating Clients with same name | 2 | 36 | August 30, 2024 | |
| Auth0 Duplicate App names | 2 | 1297 | February 15, 2023 | |
| Preventing duplicate client names | 2 | 3035 | February 5, 2021 | |
| Auth0 import is throwing error: Names must be unique | 6 | 1262 | March 23, 2023 | |
| Best Practice for Public API | 3 | 3770 | December 27, 2018 |