Connector callback protocols¶
Receive or process data using connector callbacks and compatibility protocols.
Choose a task¶
Task |
Page |
Description |
|---|---|---|
Credential callback protocol |
This entry point receives external platform verification or events, matches saved channel credentials by credential reference, and enters callback rules. |
|
List connector database names |
Returns database-name strings, unlike structured/v1 name objects and endpoint_results. No current pagination. |
|
Read connector table columns |
database/table are required; schema is optional. Returns six columns fields, distinct from structured/v1 schema_snapshot and mapping-draft objects. |
|
List schema names in a connector database |
database is required. Returns schema-name strings, not table column structures. |
|
List connector table names |
database is required and schema is optional. Returns table-name strings, discarding other location fields in transport table objects. The structured/v1 objects structure cannot be reused directly. |
|
Message connection callback protocol |
This entry point binds platform callbacks to a specified ingress connection. |
|
List MatrixOne destination database names |
Reads an external destination from the specified MatrixOne connector, requiring export_task.create and connector.use. This is not the current Workspace’s Catalog database list. Host/password input cannot replace a connector ID. |
|
List MatrixOne destination table names |
With a MatrixOne connector and database, returns destination table-name strings. Successful reads do not establish that exported data was written. |
|
Connector requests and results |
These six entry points use top-level paths and X-Workspace-ID. |
|
Two connector metadata protocols |
/connectors/db and /connectors/structured/v1 are both registered and used separately by current SDKs. |