Capabilities
Enable, disable, or configure a capability
Body is { enabled?, settings? } — at least one is required, and no
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:
adminor higher - Changing
enabledon aconnectioncapability (paystack, vertofx, merlin) requiresowner; settings-only updates on a connection stayadmin
Code Examples
Authorizations
JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"
Path Parameters
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