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

The Contacts API from Starlink — 2 operation(s) for contacts.

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

Tagged areas include Contacts. 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 4 operations across 2 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 2.

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

4 operations 2 paths 13 schemas 1 DELETE1 GET1 POST1 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 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.

Contacts 4
GET
/public/v2/contacts
Get contacts
1 param → 400401200422default403
POST
/public/v2/contacts
Create contact
body → 401400200422403
DELETE
/public/v2/contacts/{subjectId}
Delete contact
1 param → 400401403200422default
PUT
/public/v2/contacts/{subjectId}
Update contact
1 param body → 400401200422default403

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are CreateContactOnAccountRequest (6 properties), UserResponsePaginatedServiceResponse (5 properties), UserLacksRequiredPermissionServiceResponse (5 properties), UserResponseServiceResponse (5 properties). Each schema is shown below with its type and property counts.

ServiceResponse
object
4 properties
UserResponsePaginatedServiceResponse
object
5 properties
UserLacksRequiredPermissionServiceResponse
object
5 properties
UserResponseServiceResponse
object
5 properties
UserResponsePaginated
object
5 properties
ValidationResult
object
2 properties
UserLacksRequiredPermission
object
4 properties
Permission
integer
UserResponse
object
3 properties 3 required
CreateContactOnAccountRequest
object
6 properties 6 required
FeatureAccess
integer
FeaturePermission
object
2 properties 2 required
UpdateContactOnAccountRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

starlink-contacts-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 Data Pools API
Starlink Flights API
Starlink Managed Accounts API
Starlink Managed API
Starlink Mobile API
Where this information came from

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