Config API¶
Every legacy endpoint in this category and its replacement in the new Oneserve API (where one exists).
| Legacy | Status | Replacement | Notes |
|---|---|---|---|
user |
Replaced | POST /v1/users |
Legacy /rest/config/user was an upsert (create-or-update by userRef). The new API splits this into POST /v1/users (create) and PATCH /v1/users/{id} (update); pick the appropriate one based on whether the user already exists. |
clientGroup |
No replacement | — | Partial coverage in new API (Clients/Teams) but legacy is broader. |
clientGroupUpdate |
No replacement | — | Partial coverage in new API (Clients/Teams) but legacy is broader. |