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

OpenHands Secrets API

The Secrets API from OpenHands — 2 operation(s) for secrets.

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

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

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

Requests are made against 2 base URLs: https://app.all-hands.dev, http://localhost:3000.

4 operations 2 paths 5 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.53.0
Servers
https://app.all-hands.dev
http://localhost:3000
Authentication
API Key
Resource Areas
1

Authentication & Security 1

OpenHands Secrets API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Session-API-Key (APIKeyHeader).

Paths & Operations 4

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

Secrets 4
GET
/api/secrets
Load Custom Secrets Names
load_custom_secrets_names_api_secrets_get → 200
POST
/api/secrets
Create Custom Secret
create_custom_secret_api_secrets_post body → 200422
PUT
/api/secrets/{secret_id}
Update Custom Secret
update_custom_secret_api_secrets__secret_id__put 1 param body → 200422
DELETE
/api/secrets/{secret_id}
Delete Custom Secret
delete_custom_secret_api_secrets__secret_id__delete 1 param → 200422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ValidationError (3 properties), CustomSecretModel (3 properties), CustomSecretWithoutValueModel (2 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

CustomSecretWithoutValueModel
object
Custom secret model without value
2 properties 1 required
CustomSecretModel
object
Custom secret model with value
3 properties 2 required
ValidationError
object
3 properties 3 required
GETCustomSecrets
object
Custom secrets names
1 property
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openhands-secrets-api-openapi.yml Raw ↑

Other APIs OpenHands publishes across the network.

OpenHands Agent SDK
OpenHands CLI
OpenHands Local GUI REST API
OpenHands Cloud
OpenHands Add Git Providers API
OpenHands Alive API
OpenHands Conversations API
OpenHands Health API
OpenHands Options API
OpenHands Reset Settings API
OpenHands Settings API
OpenHands Unset Provider Tokens API
Where this information came from

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