Skip to main content
PUT
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

other key is accepted (400 UNKNOWN_FIELDS; credentials go to PUT /capabilities/{slug}/credentials). When settings is given it is deep-merged into the stored value (nested objects recurse, arrays replace whole, null deletes a key) and validated against the capability’s settingsSchema before enabled is applied, in one transaction — an invalid patch changes nothing. A publisher settings update also best-effort syncs the tenant’s own Publisher record; a merlin onEnable/onDisable hook provisions/tears down its scheduled import. Authorization:
  • Required role: admin or higher
  • Changing enabled on a connection capability (paystack, vertofx, merlin) requires owner; settings-only updates on a connection stay admin

Code Examples

Authorizations

Authorization
string
header
required

JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"

Path Parameters

slug
enum<string>
required

Stable identifier; never renamed after ship.

Available options:
paystack,
vertofx,
merlin,
ddex-delivery,
publisher,
distro,
release,
payment-requests,
email-branding,
catalog-media

Body

application/json
enabled
boolean
settings
object

Deep-merged patch, validated against the capability's settingsSchema.

Response

Capability updated

status
string
Example:

"success"

message
string
Example:

"Capability updated"

data
object

One entry in GET /capabilities data, and the shape of every write response's data.