Skip to main content
POST
Test a connection's stored credentials
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

already saved (there is no request body — this does not accept one-off credentials to test). A capability with no connection test, or with no credentials saved, returns 200 with data.ok: false and an explanatory data.error — not an HTTP error — since the diagnostic itself completed successfully. Only a credential rejection (reason: auth) sets connectionStatus to failed. A network or provider failure records the error and the test time but keeps the previous status, so a test run from a blocked network or during a provider outage does not switch off the routes that require the connection. The same rule applies to the test that runs after PUT /capabilities/{slug}/credentials: new credentials that cannot reach the provider stay untested. Authorization:
  • Required role: owner (the test calls the provider with the stored credentials)

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

Response

Test completed — check data.ok for the verdict

status
string
Example:

"success"

message
string
Example:

"Connection OK"

data
object