Delete profile type

DELETE 
https://acmeco.nonemployee.com/api/profile_types/:uid

Delete a profile type by UID (user-specified identifier). All profiles of that type must first be destroyed before the profile type can be destroyed.

Request

Path Parameters

uid snake_case

UID of the object to retrieve, update, or delete. A UID or "specified identifier" is a string typically in "snake_case" format that provides a human-readable description of the record. They are commonly used to ensure sandbox, qa, staging and production tenants have the identical configuration items loaded. Every record has a UID assigned when persisted. When not specified the system assigns one by default. A default value looks like a 32 character string of random hexadecimal characters.

Responses

200

Info about the operation

application/json

Schema

Schema

info
A message confirming the operation
Example: object deleted

Example (auto)

{
  "info": "object deleted"
}

400

Bad Request - unable to complete.

application/json

Schema

Schema

oneOf
InvalidJson
error
Example: Invalid JSON syntax. Please check your syntax and try again.
ValidationErrors
error
Example: The <object> failed to create/update
errors
Example: {"attribute":"can't be blank"}

Example (auto)

{
  "error": "Invalid JSON syntax. Please check your syntax and try again."
}

500

Internal Server Error - returned on unhandled exceptions.

application/json

Schema

Schema

error
A message describing the error
Example: Sorry something went wrong

Example (auto)

{
  "error": "Sorry something went wrong"
}

Authorization: http

name: bearerAuthtype: httpscheme: bearerbearerFormat: Token token=your token

• go
• powershell
  SailPoint SDK
• python
  SailPoint SDK
• csharp
• curl
• dart
• http
• java
• javascript
• kotlin
• c
• nodejs
• objective-c
• ocaml
• php
• r
• ruby
• rust
• shell
• swift

• NATIVE

Request Collapse all

Base URL

https://acmeco.nonemployee.com/api

Auth

Bearer Token

Parameters

uid — path

ResponseClear

Click the Send API Request button above and see the response here!