Update MLE Configuration for Target
PATCH/targets/:id/mle/
Allows updating MLE metadata (enabled, key_id, scope) for a target. Keys cannot be updated via PATCH - use PUT to replace entire configuration.
Request
Path Parameters
- application/json
- application/x-www-form-urlencoded
- multipart/form-data
Body
Enable or disable MLE for the target.
Update the Key ID for MLE configuration.
Update the list of URLs where MLE is applied.
Each URL must include the scheme and hostname
(e.g., ["https://api.example.com/v1/payments"]).
Body
Enable or disable MLE for the target.
Update the Key ID for MLE configuration.
Update the list of URLs where MLE is applied.
Each URL must include the scheme and hostname
(e.g., ["https://api.example.com/v1/payments"]).
Body
Enable or disable MLE for the target.
Update the Key ID for MLE configuration.
Update the list of URLs where MLE is applied.
Each URL must include the scheme and hostname
(e.g., ["https://api.example.com/v1/payments"]).
Responses
- 200
- 400
- 403
- 404
- application/json
- Schema
- Example (from schema)
Schema
Indicates if MLE is configured for the target.
Indicates if MLE is currently enabled for the target.
The Key ID for MLE configuration.
List of URLs where MLE is applied.
{
"configured": true,
"enabled": true,
"key_id": "string",
"scope": [
"string"
]
}
- application/json
- Schema
- Example (from schema)
Schema
{
"<field name>": [
"Errors related to field <field name>."
],
"non_field_errors": [
"Errors not related to any field specific field."
]
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "You do not have permission to perform this action."
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Not found."
}