configSchema.
Common choices include an API key, bearer token, OAuth application, service
account, or machine-to-machine credential. The available choices come from the
Provider Plugin rather than from a global list exposed to the caller.
Inspect a strategy
An entry insupportedAuthStrategies provides:
Handle secrets
Supply secrets only throughauthenticationConfig. Secret fields are stored
outside ordinary API records and are not returned later. Responses may include
safe, non-secret configuration or masked values, but callers must retain the
original secret if they need it elsewhere.
Validate and refresh credentials
POST /api/connectors/validatetakes acredentialMetadataIdand checks the credentials already stored for that connection against the Provider, then records the result as the connection’s credential status. It never receives or saves new credentials. The Check again action in a connection’s row on the connector page calls it. The credential must belong to the Workspace that the request names inX-Tenant. A credential of another Workspace returns404, the same as an unknown id. Parable then does not read its secret, call the Provider, or change any record.POST /api/connectors/configurereplaces saved credentials or other connection configuration.POST /api/connectors/connector-oauth-startbegins a browser OAuth flow.POST /api/connectors/connector-oauth-completecompletes that flow.GET /api/vendors/tenant-connector-credential-detailreturns safe error detail for a connection in a credential-error state.