Test Connector Connection
POST/api/v1/connectors/test
Instantiate a connector with runtime-only credentials and report connectivity. The result is a list of stages: connect, then probe for a db driver that declares PROBE_SQL. Any failed stage fails the test. A failure the request itself caused (bad credentials, an option the driver rejects) is an HTTP error carrying the structured cause (D-E5); a failure of the environment (host down, timeout) is a 200 whose connect stage failed — the request was well-formed, the target was not there.
요청
응답
- 200
- 400
- 401
- 403
- 404
- 405
- 409
- 410
- 413
- 415
- 422
- 429
- 500
- 502
- 503
- 504
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Conflict
Gone
Request Entity Too Large
Unsupported Media Type
Unprocessable Entity
Too Many Requests
Internal Server Error
Bad Gateway
Service Unavailable
Gateway Timeout