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

Starlink Routers API

The Routers API from Starlink — 10 operation(s) for routers.

Starlink Routers API is one of 16 APIs that Starlink publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Router. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

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

Requests are made against a single base URL, /api.

17 operations 10 paths 27 schemas 1 DELETE7 GET5 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://starlink.com/api/public/v2
Resource Areas
1

Paths & Operations 17

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

Routers 17
GET
/public/v2/routers/{routerId}
Get router
1 param → 400401403200422
GET
/public/v2/routers/configs
Get all router configs
1 param → 400401403200422
POST
/public/v2/routers/configs
Create router config
body → 400401403201422200
GET
/public/v2/routers/configs/{configId}
Get router config
1 param → 400401403200422
PUT
/public/v2/routers/configs/{configId}
Update router config
1 param body → 400401403200422
PUT
/public/v2/routers/configs/assign
Router config assignment
body → 400401403200422
GET
/public/v2/routers/configs/default
Get default router config
→ 401403200422
PUT
/public/v2/routers/configs/default
Set default router config
body → 400401403200422
GET
/public/v2/routers/configs/tls
Get TLS configs
1 param → 400401403200422
POST
/public/v2/routers/configs/tls
Create TLS config
body → 400401403201422200
DELETE
/public/v2/routers/configs/tls
Delete TLS config
body → 400401403200422
POST
/public/v2/routers/local-content
Upload router local content file
body → 400401403201422
GET
/public/v2/routers/local-content
Get list of router local content files
→ 401403200422
GET
/public/v2/routers/sandbox/clients
Get sandbox clients
3 params → 400401403200422
POST
/public/v2/routers/sandbox/clients
Batch update sandbox clients
body → 400401403200422
PUT
/public/v2/routers/sandbox/heartbeat
Update sandbox heartbeat
body → 400401403200422
POST
/public/v2/routers/{routerId}/reboot
Reboot router
1 param → 400401403200422

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are RouterResponseV2 (6 properties), AddRouterLocalContentResponseV2ServiceResponse (5 properties), RouterLocalContentResponseListServiceResponse (5 properties), SandboxClientResponsePaginatedServiceResponse (5 properties). Each schema is shown below with its type and property counts.

AddRouterLocalContentResponseV2
object
3 properties 3 required
UpdateBatchSandboxClientRequest
object
3 properties 3 required
RouterConfigResponseV2PaginatedServiceResponse
object
5 properties
SandboxHeartbeatRequest
object
1 property 1 required
RouterLocalContentResponse
object
4 properties
RouterConfigResponseV2Paginated
object
5 properties
UpdateDefaultConfigRequest
object
1 property 1 required
TlsConfigResponseV2
object
3 properties
RouterResponseV2
object
6 properties
TlsConfigResponseV2PaginatedServiceResponse
object
5 properties
AddRouterLocalContentResponseV2ServiceResponse
object
5 properties
DeleteTlsConfigRequest
object
1 property 1 required
RouterLocalContentResponseListServiceResponse
object
5 properties
TlsConfigCreateRequestV2
object
2 properties 2 required
SandboxClientResponsePaginatedServiceResponse
object
5 properties
SandboxClientResponse
object
3 properties
DefaultRouterConfigResponseServiceResponse
object
5 properties
ServiceResponse
object
4 properties
TlsConfigResponseV2Paginated
object
5 properties
RouterConfigResponseV2ServiceResponse
object
5 properties
ValidationResult
object
2 properties
RouterResponseV2ServiceResponse
object
5 properties
RouterConfigResponseV2
object
3 properties
RouterConfigRequest
object
2 properties 1 required
DefaultRouterConfigResponse
object
1 property
AssignRoutersConfigRequest
object
2 properties 1 required
SandboxClientResponsePaginated
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

starlink-routers-api-openapi.yml Raw ↑

Other APIs Starlink publishes across the network.

Starlink Telemetry Stream API
Starlink Local Device API
Starlink Router Local HTTPS API
Starlink Space Traffic Coordination API
Starlink Account API
Starlink Addresses API
Starlink Billing API
Starlink Contacts API
Starlink Data Pools API
Starlink Flights API
Starlink Managed Accounts API
Starlink Managed API
Where this information came from

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