Create a Reassignment Configuration
POSThttps://sailpoint.api.identitynow.com/v2024/reassignment-configurations
This API is currently in an experimental state. The API is subject to change based on feedback and further testing. You must include the X-SailPoint-Experimental header and set it to true
to use this endpoint.
Creates a new Reassignment Configuration for the specified identity.
Request
Header Parameters
Use this header to enable this experimental API.
true
- application/json
Bodyrequired
The identity id to reassign an item from
2c91808781a71ddb0181b9090b5c504e
The identity id to reassign an item to
2c91808781a71ddb0181b9090b53504a
Enum list of valid work types that can be selected for a Reassignment Configuration
Possible values: [ACCESS_REQUESTS
, CERTIFICATIONS
, MANUAL_TASKS
]
ACCESS_REQUESTS
The date from which to start reassigning work items
2022-07-21T11:13:12.345Z
The date from which to stop reassigning work items. If this is an null string it indicates a permanent reassignment.
2022-07-30T17:00:00.000Z
Responses
- 201
- 400
- 401
- 403
- 429
- 500
The newly created Reassignment Configuration object
- application/json
- Schema
- Example (auto)
Schema
identity object
configDetails object[]
{
"identity": {
"id": "2c91808380aa05580180aaaaf1940410",
"name": "William Wilson"
},
"configDetails": [
{
"configType": "ACCESS_REQUESTS",
"targetIdentity": {
"id": "2c91808380aa05580180aaaaf1940410",
"name": "William Wilson"
},
"startDate": "2022-07-21T11:13:12.345Z",
"endDate": "0001-01-01T00:00:00Z",
"auditDetails": {
"created": "2022-07-21T11:13:12.345Z",
"createdBy": {
"id": "2c91808380aa05580180aaaaf1940410",
"name": "William Wilson"
},
"modified": "2022-07-21T11:13:12.345Z",
"modifiedBy": {
"id": "2c91808380aa05580180aaaaf1940410",
"name": "William Wilson"
}
}
}
]
}
Client Error - Returned if the request body is invalid.
- application/json
- Schema
- Example (auto)
Schema
Fine-grained error code providing more detail of the error.
400.1 Bad Request Content
Unique tracking id for the error.
e7eab60924f64aa284175b9fa3309599
messages object[]
causes object[]
{
"detailCode": "400.1 Bad Request Content",
"trackingId": "e7eab60924f64aa284175b9fa3309599",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
}
],
"causes": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
}
]
}
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
- application/json
- Schema
- Example (auto)
Schema
A message describing the error
JWT validation failed: JWT is expired
{
"error": "JWT validation failed: JWT is expired"
}
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
- application/json
- Schema
- Example (auto)
- 403
Schema
Fine-grained error code providing more detail of the error.
400.1 Bad Request Content
Unique tracking id for the error.
e7eab60924f64aa284175b9fa3309599
messages object[]
causes object[]
{
"detailCode": "400.1 Bad Request Content",
"trackingId": "e7eab60924f64aa284175b9fa3309599",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
}
],
"causes": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
}
]
}
An example of a 403 response object
{
"detailCode": "403 Forbidden",
"trackingId": "b21b1f7ce4da4d639f2c62a57171b427",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The server understood the request but refuses to authorize it."
}
]
}
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
- application/json
- Schema
- Example (auto)
Schema
A message describing the error
Rate Limit Exceeded
{
"message": " Rate Limit Exceeded "
}
Internal Server Error - Returned if there is an unexpected error.
- application/json
- Schema
- Example (auto)
- 500
Schema
Fine-grained error code providing more detail of the error.
400.1 Bad Request Content
Unique tracking id for the error.
e7eab60924f64aa284175b9fa3309599
messages object[]
causes object[]
{
"detailCode": "400.1 Bad Request Content",
"trackingId": "e7eab60924f64aa284175b9fa3309599",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
}
],
"causes": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
}
]
}
An example of a 500 response object
{
"detailCode": "500.0 Internal Fault",
"trackingId": "b21b1f7ce4da4d639f2c62a57171b427",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "An internal fault occurred."
}
]
}
Authorization: oauth2
type: Personal Access Tokenscopes: idn:reassignment-configuration:create
- go
- powershellSailPoint SDK
- pythonSailPoint SDK
- csharp
- curl
- dart
- http
- java
- javascript
- kotlin
- c
- nodejs
- objective-c
- ocaml
- php
- r
- ruby
- rust
- shell
- swift
- NATIVE