Configure or Replace Message Signature
PUT/targets/:id/signature/
Creates a new signature configuration or completely replaces an existing one for the specified target. Enabling is implicit on successful creation/replacement.
Request
Path Parameters
- application/json
- multipart/form-data
Body
required
The signature method to configure. Must be one of: xpay, http-v1, jwt-v1.
Body
required
The signature method to configure. Must be one of: xpay, http-v1, jwt-v1.
The key ID for JWT v1 signature method.
The merchant ID for JWT v1 signature method.
Possible values: Value must match regular expression (?:p12|pfx)$
The .p12 file containing the client certificate and private key.
Password to decrypt the .p12 file.
Responses
- 200
- 400
- 401
- 403
- 404
- 500
- application/json
- Schema
- Example (from schema)
Schema
Indicates if message signature is configured for the target.
Indicates if message signature is currently enabled for the target.
The signature method configured for the target.
Returns null if signature is not configured.
{
"configured": true,
"enabled": true,
"signature_method": "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": "Incorrect authentication credentials."
}
- 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."
}
- application/json
- Schema
- Example (from schema)
Schema
{
"detail": "Unexpected error while handling your request."
}