Skip to main content

Run a connection test for one integration (side-effecting; requires integrations:write)

POST 
/v1/integrations/:integration_id/test

Run the product's connectivity check against one integration.

The check uses the integration's own stored credentials — you never send them — and returns just whether it succeeded and a message. No credential is echoed back.

This deliberately requires the integrations:write scope rather than read: it makes a live outbound call to the provider using stored credentials, which can consume rate limits or trigger account lockouts, so a leaked read-only key must not be able to fire it.

Request​

Responses​

Successful Response

Last updated on