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

TensorDock Secrets API

The TensorDock Secrets API (v2) for managing SSH keys and generic secrets that are encrypted at rest and in transit and can be attached to instances at deploy time. Two secret types are supported — `SSHKEY` for SSH authentication and `SECRET`/`GENERIC` for application credentials whose values are not returned after creation.

TensorDock Secrets API is one of 9 APIs that TensorDock publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include GPU, Cloud, Secrets, SSH Keys, and Credentials. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 4 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://dashboard.tensordock.com.

4 operations 2 paths 4 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Server
https://dashboard.tensordock.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

TensorDock Secrets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Key) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token authentication. Generate API tokens at https://dashboard.tensordock.com/api. Send the token in the Authorization: Bearer header.

Paths & Operations 4

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

Secrets 4

Manage SSH keys and generic secrets

GET
/api/v2/secrets
List Secrets
listSecrets → 200
POST
/api/v2/secrets
Create Secret
createSecret body → 201
GET
/api/v2/secrets/{id}
Get Secret
getSecret 1 param → 200
DELETE
/api/v2/secrets/{id}
Delete Secret
deleteSecret 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Secret (3 properties), SecretListResponse (1 property), CreateSecretRequest (1 property), SecretResponse (1 property). Each schema is shown below with its type and property counts.

SecretResponse
object
1 property
CreateSecretRequest
object
1 property 1 required
Secret
object
3 properties
SecretListResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tensordock-secrets-api-openapi.yml Raw ↑

Other APIs TensorDock publishes across the network.

TensorDock Instances API
TensorDock Authorization API
TensorDock Billing API
TensorDock Containers API
TensorDock Hostnodes API
TensorDock Instant VMs API
TensorDock Spot API
TensorDock Virtual Machines API
Where this information came from

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