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 User API

The User API from OpenHands — 8 operation(s) for user.

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

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

This API exposes 8 operations across 8 paths, and defines 11 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.

8 operations 8 paths 11 schemas 8 GET

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 User API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Session-API-Key (APIKeyHeader).

Paths & Operations 8

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

User 8
GET
/api/user/installations
Get User Installations
get_user_installations_api_user_installations_get 1 param → 200422
GET
/api/user/repositories
Get User Repositories
get_user_repositories_api_user_repositories_get 5 params → 200422
GET
/api/user/info
Get User
get_user_api_user_info_get → 200
GET
/api/user/search/repositories
Search Repositories
search_repositories_api_user_search_repositories_get 5 params → 200422
GET
/api/user/suggested-tasks
Get Suggested Tasks
get_suggested_tasks_api_user_suggested_tasks_get → 200
GET
/api/user/repository/branches
Get Repository Branches
get_repository_branches_api_user_repository_branches_get 1 param → 200422
GET
/api/user/repository/{repository_name}/microagents
Get Repository Microagents
get_repository_microagents_api_user_repository__repository_name__microagents_get 1 param → 200422
GET
/api/user/repository/{repository_name}/microagents/content
Get Repository Microagent Content
get_repository_microagent_content_api_user_repository__repository_name__microagents_content_get 2 params → 200422

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Repository (9 properties), User (6 properties), SuggestedTask (5 properties), Branch (4 properties). Each schema is shown below with its type and property counts.

Repository
object
9 properties 4 required
TaskType
string
SuggestedTask
object
5 properties 5 required
OwnerType
string
ValidationError
object
3 properties 3 required
MicroagentResponse
object
Response model for microagents endpoint. Note: This model only includes basic metadata that can be determined without parsing microagent content. Use the separ…
3 properties 3 required
ProviderType
string
MicroagentContentResponse
object
Response model for individual microagent content endpoint.
4 properties 2 required
Branch
object
4 properties 3 required
User
object
6 properties 3 required
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openhands-user-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 Secrets API
OpenHands Settings API
Where this information came from

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