Update a custom API connector
Update a custom API connector. Every field is optional; omitted fields keep their stored value, and a blank access_token keeps the stored credential. Moving base_api_url or test_url to a new origin (scheme, host or port) requires a new access_token in the same request and replaces the stored refresh token with the request’s refresh_token, if any. Only custom API connectors can be updated here; other providers answer 404. Requires full access.
Authorizations
Body
Update custom API connector request
Replacement credential. Omitted or blank values keep the stored credential and leave refresh_token untouched; they are rejected with 422 when base_api_url or test_url moves to an origin the stored credential was not entered for. Stored encrypted and never returned.
"sk-live-..."
Replacement refresh token, applied only together with a non-empty access_token; sent on its own it changes nothing. Omit it to keep the stored refresh token, except when the update moves the connector to a new origin: then the stored refresh token is dropped. An empty string sent with a new access_token stores an empty refresh token.
"rt-..."