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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
TetraScience

TetraScience Connectors API

The Connectors API from TetraScience — 23 operation(s) for connectors.

Documentation Provider Profile APIs.io OpenAPI GitHub

TetraScience Connectors API is one of 35 APIs that TetraScience 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, API documentation, a getting-started guide, an API reference, a changelog, and authentication docs.

This API exposes 23 operations across 23 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 4.0.

Requests are made against 5 base URLs: https://api.tetrascience.com, https://api.tetrascience-uat.com, https://api.tetrascience-dev.com, https://api.tetrascience-uat.com, api.tetrascience.com.

23 operations 23 paths 28 schemas 21 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0
Base URL
https://api.tetrascience.com
Authentication
API Key, API Key, API Key
Contact
TetraScience
License
Proprietary
Resource Areas
1

Authentication & Security 3

TetraScience Connectors API declares 3 security schemes for authenticating requests. An API key is passed in the header as ts-auth-token (token). An API key is passed in the header as x-org-slug (orgSlug). An API key is passed in the header as ts-auth-token (tsAuthToken). By default, every request must be authenticated.

  • token — JWT Token for authentication
  • orgSlug — Your organization slug

Paths & Operations 23

Across 23 paths, the API surfaces 23 operations — 21 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Connectors 23
GET
/v1/data-acquisition/connectors
Get all Connectors
ConnectorController_getAll → 200
GET
/v1/data-acquisition/connectors/{id}
Get a Connector by id
ConnectorController_getById 3 params → 200
GET
/v1/data-acquisition/connectors/{id}/metrics
Get a Connector's metrics
ConnectorController_getFileMetrics 1 param → 200
GET
/v1/data-acquisition/connectors/{id}/files
Get a Connector's reported files
ConnectorController_getFiles 15 params → 200
GET
/v1/data-acquisition/connectors/{id}/files/stats
Get statistics about a Connector's files
ConnectorController_getFileStats 1 param → 200
GET
/v1/artifacts/connectors/{namespace}
List all Connectors for namespace
getConnectorArtifactByNamespace 3 params → 200404
GET
/v1/artifacts/connectors/{namespace}/{slug}
Returns a list of Connector artifacts given a namespace and slug
getConnectorArtifactByNamespaceAndSlug 4 params → 200404
GET
/v1/artifacts/connectors/{namespace}/{slug}/{version}/files/{fileSlug}
Get contents for an Connector file
getConnectorArtifactByNamespaceSlugAndFileSlug 6 params → 200400404
GET
/v1/artifacts/connectors/{namespace}/{slug}/{version}
Get single Connector
getConnectorArtifactByNamespaceSlugAndVersion 4 params → 200404
GET
/v1/artifacts/connectors/{namespace}/{slug}/{version}/files
Get available file slugs for Connector
getConnectorArtifactFileSlugs 4 params → 200400404
GET
/v1/artifacts/connectors/{namespace}/{slug}/{version}/labels
Get labels for an Connector
getConnectorArtifactLabels 4 params → 200404
GET
/v1/artifacts/connectors/{namespace}/{slug}/{version}/relationships
Get artifacts related to Connector
getConnectorArtifactRelationships 4 params → 200404
GET
/v1/artifacts/connectors
List all connectors artifacts
getConnectorArtifacts 3 params → 200
GET
/v1/artifacts/data-apps/{namespace}
List all Data Apps for namespace
getDataAppArtifactByNamespace 3 params → 200404
GET
/v1/artifacts/data-apps/{namespace}/{slug}
Returns a list of Data App artifacts given a namespace and slug
getDataAppArtifactByNamespaceAndSlug 4 params → 200404
GET
/v1/artifacts/data-apps/{namespace}/{slug}/{version}/files/{fileSlug}
Get contents for a Data App file
getDataAppArtifactByNamespaceSlugAndFileSlug 6 params → 200400404
GET
/v1/artifacts/data-apps/{namespace}/{slug}/{version}
Get single Data App
getDataAppArtifactByNamespaceSlugAndVersion 4 params → 200404
GET
/v1/artifacts/data-apps/{namespace}/{slug}/{version}/files
Get available file slugs for Data App
getDataAppArtifactFileSlugs 4 params → 200400404
GET
/v1/artifacts/data-apps/{namespace}/{slug}/{version}/labels
Get labels for a Data App
getDataAppArtifactLabels 4 params → 200404
GET
/v1/artifacts/data-apps/{namespace}/{slug}/{version}/relationships
Get artifacts related to Data App
getDataAppArtifactRelationships 4 params → 200404
GET
/v1/artifacts/data-apps
List all connectors artifacts of sub-type data-app
getDataAppArtifacts 3 params → 200404
POST
/v1/artifacts/connectors/search
Search for items
searchConnectors 3 params → 200
POST
/v1/artifacts/data-apps/search
Search for items
searchDataApps 3 params → 200404

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are HubDto (29 properties), ConnectorDetailsDto (21 properties), ConnectorDto (20 properties), ArtifactObjectBase (9 properties). Each schema is shown below with its type and property counts.

LabelList
array
HubStatusDto
object
5 properties 5 required
ConnectorFilesResponse
object
A list of files reported by a Connector.
2 properties 2 required
ConnectorDto
object
Details of a single Connector
20 properties 16 required
GetConnectorMetricsDto
object
The set of metrics reported by the Connector.
1 property 1 required
SupportedPlatformVersion
object
2 properties
ConnectorDetailsDto
object
Details of a single Connector.
21 properties 17 required
ConnectorObject
GetConnectorFileStatsDto
object
The file stats reported by a Connector.
6 properties 6 required
HubDto
object
29 properties 14 required
ConnectorCustomRouteUiComponentDto
object
4 properties 4 required
ArtifactDto
object
3 properties 4 required
MetricTimeValueDto
object
A metric time-value pair reported by a Connector.
2 properties 2 required
ArtifactDetailsDto
object
This is the detailed version of the ArtifactDto. Includes dynamic fields from the artifact's manifest, so not all response keys are listed here.
7 properties 8 required
Relationships
object
4 properties
ConnectorObjectList
array
ConnectorFileDto
object
A file reported by a Connector.
9 properties 8 required
ConnectorGeneratedConfigUiComponentDto
object
3 properties 3 required
ArtifactNamespace
string
HubHostDto
object
4 properties 4 required
ConnectorsResponse
object
A list of Connectors
1 property 1 required
ConnectorFileSlug
string
ConnectorCustomConfigUiComponentDto
object
3 properties 3 required
Key
object
4 properties 4 required
ConnectorMetricDto
object
A set of metric values reported by a Connector.
2 properties 2 required
ArtifactObjectBase
object
9 properties 5 required
LabelDto
object
3 properties 3 required
ConnectorUiDto
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tetrascience-connectors-api-openapi.yml Raw ↑

Other APIs TetraScience publishes across the network.

TetraScience Access Groups API
AE Profile APIs.io
TetraScience Agents API
AE Profile APIs.io
TetraScience ai-workflows API
AE Profile APIs.io
TetraScience Attributes API
AE Profile APIs.io
TetraScience Audit Trail API
AE Profile APIs.io
TetraScience clusters API
AE Profile APIs.io
TetraScience Commands API
AE Profile APIs.io
TetraScience Data Acquisition API
AE Profile APIs.io
TetraScience Data App Providers API
AE Profile APIs.io
TetraScience Data Apps API
AE Profile APIs.io
TetraScience databricks API
AE Profile APIs.io
TetraScience Edit Subscriptions API
AE Profile APIs.io
#Connectors
← Back to T APIs
API Details
ID
tetrascience:tetrascience-connectors-api
Base URL
https://api.tetrascience.com
Docs
https://developers.tetrascience.com/
Provider
TetraScience
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=tetrascience-connectors-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tetrascience-connectors-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of TetraScience 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.