How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Structify connectors API

The connectors API from Structify — 24 operation(s) for connectors.

Structify connectors API is one of 32 APIs that Structify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Connectors. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 29 operations across 24 paths, and defines 152 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 2 base URLs: https://api.structify.ai, http://localhost:8080.

29 operations 24 paths 152 schemas 3 DELETE15 GET4 PATCH5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.structify.ai
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Structify connectors API declares 2 security schemes for authenticating requests. An API key is passed in the header as api_key (api_key). It accepts HTTP bearer tokens (session_token). By default, every request must be authenticated.

Paths & Operations 29

Across 24 paths, the API surfaces 29 operations — 3 DELETE, 15 GET, 4 PATCH, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

connectors 29
PUT
/connector-type-snippets/{connector_type}
upsert_connector_type_snippet 1 param body → 200401
GET
/connectors
list_connectors 2 params → 200401403
POST
/connectors
create_connector body → 201400401403500
PATCH
/connectors/clarification-requests/{clarification_id}/resolve
Mark a clarification request as resolved
resolve_clarification 1 param → 200401403404
PATCH
/connectors/columns/{column_id}
Update column metadata (notes)
update_column 1 param body → 200401403404
GET
/connectors/search-tables
search_tables 2 params → 200401
GET
/connectors/stores
list_connector_stores → 200401
POST
/connectors/summaries
list_connector_summaries body → 200400401404
PATCH
/connectors/tables/{table_id}
Update table metadata (description or notes)
update_table 1 param body → 200401403404
GET
/connectors/tables/{table_id}/lineage
get_table_lineage 1 param → 200404
GET
/connectors/tables/{table_id}/path
get_connector_table_path 1 param → 200404
GET
/connectors/with-snippets
list_connectors_with_snippets → 200401
DELETE
/connectors/{connector_id}
delete_connector 1 param → 204401403404
GET
/connectors/{connector_id}
get_connector 1 param → 200401403404
PATCH
/connectors/{connector_id}
update_connector 1 param body → 200400401403404
GET
/connectors/{connector_id}/clarification-requests
Get all clarification requests for a connector
get_connector_clarification_requests 1 param → 200403404
POST
/connectors/{connector_id}/explore
explore_connector 1 param body → 200400403404
GET
/connectors/{connector_id}/explore/active-run
get_active_exploration_run 1 param → 200403404
GET
/connectors/{connector_id}/explore/chat
Get chats from connector exploration (requires debug permission)
get_connector_explorer_chat 5 params → 200400403404
GET
/connectors/{connector_id}/explore/runs
Get all exploration runs for a connector (requires debug permission)
get_connector_exploration_runs 1 param → 200403404
GET
/connectors/{connector_id}/explore/runs/{run_id}/progress
get_exploration_run_progress 2 params → 200403404
DELETE
/connectors/{connector_id}/schema_object
delete_connector_schema_object 1 param body → 200400403404
POST
/connectors/{connector_id}/schema_object
add_connector_schema_object 1 param body → 201400403404
POST
/connectors/{connector_id}/secrets
create_connector_secret 1 param body → 201400401404
DELETE
/connectors/{connector_id}/secrets/{secret_name}
delete_connector_secret 2 params → 204401404
GET
/connectors/{connector_id}/store
get_connector_store 1 param → 200401403404
GET
/connectors/{connector_id}/tables
List all tables for a connector
list_connector_tables 1 param → 200403404
GET
/internal/connectors/{connector_id}/datahub-artifacts/{kind}
connectors_download_datahub_artifact 3 params → 200403404
PUT
/internal/connectors/{connector_id}/datahub-artifacts/{kind}
connectors_upload_datahub_artifact 3 params body → 204403404

Schemas 152

The contract defines 152 schemas that model the data the API accepts and returns. The most detailed are Job (21 properties), Connector (19 properties), UpdateConnector (13 properties), ClarificationRequest (11 properties). Each schema is shown below with its type and property counts.

ConnectorExplorerChatId
string
DecodingParams
object
1 property 1 required
ToolResult
ConnectorStoreResponse
object
1 property
Verbosity
string
ConnectorTableResult
object
6 properties 4 required
ConnectorColumnId
string
ClarificationRequestId
string
SaveMemoryInput
object
2 properties 2 required
ExitInput
object
1 property 1 required
DeleteFileInput
object
1 property 1 required
InspectStepInput
object
1 property 1 required
ConnectorTable
object
Represents a table (for relational databases) or resource (for APIs)
6 properties 3 required
CreatedSchemaObject
ExplorationPhaseId
Identifies the phase of connector exploration This enum is used to track which phase of exploration a chat session belongs to. It's stored as JSONB in the data…
RequiredEntity
object
2 properties 1 required
ExplorationProgress
object
2 properties 1 required
DatahubSecretMap
object
Maps DatahubIngestionKey to the name of the connector secret that holds the value.
ApiExecuteInput
object
1 property 1 required
SaveRequirement
It's an OR statement across these.
RequiredProperty
object
2 properties 2 required
ConnectorTypeSnippet
object
5 properties 4 required
MembershipId
string
SaveApiResourceInput
object
4 properties 2 required
SaveSchemaInput
object
3 properties 1 required
Connector
object
19 properties 8 required
BasicPropValue
ImageMeta
object
4 properties 1 required
ViewPageInput
object
1 property 1 required
InternalErrorKind
string
Categorizes the kind of internal error that occurred during LLM generation. This allows the frontend to render appropriate error messages without regex matchin…
NodeSummary
object
4 properties 2 required
ExplorationRun
object
7 properties 4 required
RequestClarificationInput
object
3 properties 2 required
MergeStrategy
RerankResult
object
3 properties 2 required
ConnectorExplorerChat
object
Connector explorer chat with deserialized ChatPrompt for API responses
7 properties 7 required
FormatterMeta
NewSchemaObject
ExplorerChatResponse
object
1 property 1 required
ConnectorId
string
AddDependencyInput
object
2 properties 1 required
LineageType
string
Lineage type for table-to-table relationships
PhaseActivity
object
4 properties 3 required
ExplorationStatus
string
SpeakerTag
string
ConnectorTableSearchResult
object
Result struct for connector table search
5 properties 5 required
ChatEvent
Events in a chat session timeline, including messages and unified tool calls/results
JobStatus
string
LLMRelationship
object
4 properties 3 required
LLMEntity
object
3 properties 3 required
CreateConnectorInput
object
4 properties 2 required
ReadNodeLogsInput
object
2 properties 1 required
UpdateTableRequest
object
2 properties
ConnectorTableId
string
TextMeta
object
1 property 1 required
TableLineageResponse
object
Response for table lineage queries containing both upstream and downstream dependencies
2 properties 2 required
RunBashInput
object
3 properties 1 required
CodeExecutionResult
object
3 properties 3 required
SaveInput
object
3 properties 3 required
PropertyDescriptor
object
4 properties 2 required
SaveColumnInput
object
3 properties 2 required
ConnectorWithSecretsAndValues
GetSecretResult
object
Result of getting a secret
4 properties 4 required
ConnectorSummary
object
3 properties 2 required
JobType
string
ExplorationRunId
string
ScraperMeta
object
2 properties 2 required
ConnectorCategory
string
RequiredRelationship
object
1 property 1 required
WorkflowSessionNodeId
string
LLMKnowledgeGraph
object
Knowledge graph info structured to deserialize and display in the same format that the LLM outputs. Also the first representation of an LLM output in the pipel…
2 properties 1 required
CreateConnectorRequest
object
5 properties 2 required
Job
object
21 properties 9 required
RelationshipMergeProbability
object
2 properties
ConnectorDatabaseId
string
ToolInvocation
WebSearchInput
object
1 property 1 required
WebMeta
object
4 properties 2 required
UpdateConnectorRequest
ConnectorWithSnippets
ConnectorSchemaInfo
object
Schema within a database
5 properties 3 required
DocSnippet
object
3 properties 3 required
SearchConnectorTablesInput
object
2 properties 1 required
TeamVisibility
string
ConnectorDatabaseInfo
object
Database within a connector
5 properties 3 required
ChatSessionRole
string
Flag
object
10 properties 4 required
MergeConfig
object
The configuration for a probabilistic merge strategy
3 properties 2 required
DeleteSchemaObjectRequest
UpdateColumnRequest
object
1 property
ConnectorSchemaId
string
DecodingParamEnum
ActionDef
object
Action definition
2 properties 2 required
DatasetId
string
UpdateConnector
object
13 properties
ConnectorColumnResult
object
3 properties 2 required
ImageResult
object
2 properties 1 required
ChatPrompt
object
3 properties 3 required
MessageContent
RunPythonInput
object
4 properties 1 required
TeamId
string
ExploreConnectorRequest
object
4 properties
ConnectorWithSecrets
SaveTableInput
object
3 properties 1 required
DatahubProgress
object
8 properties 8 required
InfiniteScrollInput
object
ConnectorTableInfo
object
3 properties 2 required
AddSchemaObjectRequest
EntityId
string
MoveFileInput
object
2 properties 2 required
ComparisonStrategy
string
UpdateTableResponse
object
1 property 1 required
RunPipelineInput
object
1 property
ListTablesResponse
object
1 property 1 required
IssueFoundInput
object
3 properties 3 required
SelectDataInput
object
1 property 1 required
UpsertConnectorTypeSnippetRequest
object
1 property
SchemaObjectId
JobId
string
WebNavigateOutput
string
UserId
string
DatasetDescriptor
object
A dataset is where you put multiple referential schemas. A dataset is a complete namespace where all references between schemas are held within the dataset.
5 properties 4 required
WebNavigateInput
object
2 properties 1 required
LlmInformationStore
object
Information store for connector schema Hierarchical structure: Connector → Database → Schema → Table → Column Works for both relational databases and API-based…
2 properties 2 required
TableDescriptor
object
The full definition of what a schema is - without duplicate information.
5 properties 3 required
ConnectorSummariesRequest
object
1 property 1 required
SecretSummary
object
Response model for listing secrets (without sensitive data)
3 properties 3 required
PropertyType
TableLineageItem
object
A single table in a lineage relationship
5 properties 5 required
SaveEntitiesInput
object
3 properties 3 required
ReasoningEffort
string
ClarificationRequestsResponse
object
1 property 1 required
PinPreviousToolInput
object
1 property 1 required
NavigateToIFrameInput
object
1 property 1 required
DeleteSchemaObjectResponse
object
2 properties 2 required
ApplyPatchEdit
object
2 properties 2 required
ErrorResponse
object
Standard error response
1 property 1 required
ConnectorColumn
object
Represents a column in a table or API resource
4 properties 3 required
AddSchemaObjectResponse
ConnectorTablePathResponse
object
4 properties 4 required
PromptMeta
object
All metadata required to generate a prompt for the LLM
5 properties 4 required
RelationshipDescriptor
object
6 properties 4 required
JavascriptInput
object
1 property 1 required
TableSearchResults
object
3 properties 3 required
SaveDatabaseInput
object
3 properties 1 required
Message
object
Our generic definition of a message to a chat agent.
2 properties 2 required
RelationshipMergeStrategy
ClarificationRequest
object
11 properties 6 required
SearchConnectorTypesInput
object
1 property
ExplorationRunsResponse
object
1 property 1 required
CreateSecretRequest
object
2 properties 2 required
ApplyPatchInput
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

structify-connectors-api-openapi.yml Raw ↑

Other APIs Structify publishes across the network.

Structify account API
Structify admin API
Structify chat API
Structify chat_templates API
Structify code API
Structify connector_catalog API
Structify dataset API
Structify documents API
Structify entity API
Structify jobs API
Structify match API
Structify Nango API
Where this information came from

This is an independent, third-party profile of Structify connectors API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.