/profiles/{id_or_name}Delete a profile by its ID or by its name.
Authorization
bearerAuth In: header
Path Parameters
Profile ID or profile name
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/profiles/string"{ "code": "string", "message": "string", "details": [ { "code": "string", "message": "string" } ], "inner_error": { "code": "string", "message": "string" }}{ "code": "string", "message": "string", "details": [ { "code": "string", "message": "string" } ], "inner_error": { "code": "string", "message": "string" }}{ "code": "string", "message": "string", "details": [ { "code": "string", "message": "string" } ], "inner_error": { "code": "string", "message": "string" }}{ "code": "string", "message": "string", "details": [ { "code": "string", "message": "string" } ], "inner_error": { "code": "string", "message": "string" }}{ "code": "string", "message": "string", "details": [ { "code": "string", "message": "string" } ], "inner_error": { "code": "string", "message": "string" }}Rename profile by ID or name PATCH
Update a profile's name. Names must be unique within the logical project; during the default-project migration, unscoped profiles and profiles in the org default project are treated as the same project. Duplicate-name conflicts are checked before update but are best-effort because there is no backing unique index. Renaming a profile while a browser session references it by name may prevent that session's changes from saving; prefer renaming when the profile is not in use.
Download profile archive GET
Returns a zstd-compressed tar file of the full user-data directory.