Assume User
POST/api
Assume the identity of another user, the assumed user will be stored in the session and used for all subsequent requests until the session is cleared
Request
Header Parameters
Ftrack-Api-Options any
Api options formatted as key value pairs separated by semicolon.
Suported values are:
- denormalize
- strict
denormalize - data is not normalised before sent to client which means there is no need to merge entities client side.
Must also have strict option enabled.
strict - only requested data is loaded and returned to the client
Examples:
denormalize=1;strict=1
denormalize=False;strict=True
denormalize=false;strict=false
Ftrack-Api-Key any
API key used to authenticate. API keys are created from Settings under the page API keys.
Ftrack-User any
Username used to authenticate.
- application/json
Body
array
required
Array [
]
action Actionrequired
Possible values: [assume_user
]
user_id uuidrequired
read_only Read Only
Default value: true
metadata
object
property name* any
Responses
- 200
- 422
Successful Response
Validation Error
- application/json
- Schema
- Example (from schema)
Schema
Array [
Array [
- MOD1
- MOD2
]
]
detail
object[]
loc
object[]
required
anyOf
string
integer
msg Messagerequired
type Error Typerequired
{
"detail": [
{
"loc": [
"string",
0
],
"msg": "string",
"type": "string"
}
]
}
Loading...