> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valar.space/llms.txt
> Use this file to discover all available pages before exploring further.
# List state vectors for one or more spacecraft
> Retrieves a paginated list of state vectors for the specified spacecraft(s), with optional date range filtering. The spacecraftId parameter may be repeated to query multiple spacecraft in a single call (e.g. ?spacecraftId=A&spacecraftId=B); results are merged into a single paginated set. Results are sorted by epoch descending by default. Empty results return 200 with an empty page.
## OpenAPI
````yaml https://api.valar.space/api-docs/mintlify get /operations/state-vectors
openapi: 3.0.1
info:
contact:
email: api@valar.space
name: Valar Space
url: https://valar.space
description: >-
Welcome to the documentation for the Valar Operations API, here are some
quick tips if you just landed!
- The top level elements are the
Resources accessible via the API and the different queries used to
interact with each resource via the appropriate HTTP method call.
-
You can expand each method to get further information on the expected input
parameters and the different responses that can be received.
- For
both the input parameters and responses, an Example is present for
clarification.
- For further details, the example snipped can be
switched to Schema view, where a detailed explanation of each element
can be found.
- The Try it out button can be used to call the
API directly from the documentation page, which allows for some easy testing
and also provides the equivalent 'curl' command line code for easy
portability of the call execution.
- Before starting, remember
to use the token endpoint and activate the token with the Authorize
button.
title: API Documentation
version: 1.0.0
servers:
- url: /
description: Default Server URL
- url: https://api.valar.space
description: API Server
security:
- apiKeyAuth: []
tags:
- description: >-
Operations for managing state vectors — listing, importing, exporting, and
deleting spacecraft state data
name: State Vectors
paths:
/operations/state-vectors:
get:
tags:
- State Vectors
summary: List state vectors for one or more spacecraft
description: >-
Retrieves a paginated list of state vectors for the specified
spacecraft(s), with optional date range filtering. The spacecraftId
parameter may be repeated to query multiple spacecraft in a single call
(e.g. ?spacecraftId=A&spacecraftId=B); results are merged into a single
paginated set. Results are sorted by epoch descending by default. Empty
results return 200 with an empty page.
operationId: getStateVectors
parameters:
- description: >-
Spacecraft identifier(s) to filter state vectors by. Required; may
be repeated to query multiple spacecraft in a single call (e.g.
?spacecraftId=A&spacecraftId=B), in which case results are merged
into a single paginated set sorted by epoch desc.
example: 550e8400-e29b-41d4-a716-446655440000
in: query
name: spacecraftId
required: true
schema:
maxItems: 50
minItems: 1
type: array
items:
type: string
- description: Start of date range filter (inclusive, ISO-8601)
example: '2025-01-01T00:00:00Z'
in: query
name: startDate
required: false
schema:
type: string
format: date-time
- description: End of date range filter (inclusive, ISO-8601)
example: '2025-01-02T00:00:00Z'
in: query
name: endDate
required: false
schema:
type: string
format: date-time
- in: query
name: pageable
required: true
schema:
$ref: '#/components/schemas/Pageable'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/PaginatedResponse'
description: Successfully retrieved state vectors
'400':
content:
application/json:
example:
timestamp: '2025-01-15T10:30:00.000Z'
status: 400
error: Bad Request
message: Required parameter 'spacecraftId' is not present
path: /operations/state-vectors
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Invalid request parameters
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/BearerTokenErrorResponse'
description: Not authenticated — missing or invalid bearer token
'403':
content:
application/json:
example:
timestamp: '2025-01-15T10:30:00.000Z'
status: 403
error: ACCESS_ERROR
message: Access denied
path: /operations/state-vectors
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Insufficient permissions
'500':
content:
application/json:
example:
timestamp: '2025-01-15T10:30:00.000Z'
status: 500
error: Internal Server Error
message: An unexpected error occurred
path: /operations/state-vectors
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Internal server error
components:
schemas:
Pageable:
type: object
properties:
page:
minimum: 0
type: integer
format: int32
size:
minimum: 1
type: integer
format: int32
sort:
type: array
items:
type: string
PaginatedResponse:
type: object
properties:
content:
type: array
description: List of items in the current page
items:
type: object
description: List of items in the current page
empty:
type: boolean
description: Whether the content list is empty
example: false
first:
type: boolean
description: Whether this is the first page
example: true
hasNext:
type: boolean
description: Whether there are more pages after this one
example: true
hasPrevious:
type: boolean
description: Whether there are pages before this one
example: false
last:
type: boolean
description: Whether this is the last page
example: false
page:
type: integer
description: Current page number (0-indexed)
format: int32
example: 0
size:
type: integer
description: Number of items per page
format: int32
example: 20
totalElements:
type: integer
description: Total number of elements across all pages
format: int64
example: 150
totalPages:
type: integer
description: Total number of pages
format: int32
example: 8
description: >-
Paginated response wrapper containing a page of results with navigation
metadata
ErrorResponse:
type: object
properties:
details:
type: object
additionalProperties:
type: object
description: Structured error details with scenario-specific context fields
nullable: true
description: Structured error details with scenario-specific context fields
nullable: true
error:
type: string
description: HTTP status reason phrase or error category
example: Bad Request
fieldErrors:
type: object
additionalProperties:
type: string
description: >-
Per-field validation error messages, present only for validation
errors
nullable: true
description: >-
Per-field validation error messages, present only for validation
errors
nullable: true
message:
type: string
description: Detailed error message
example: Validation failed
path:
type: string
description: The request path where the error occurred
example: /measurements
status:
type: integer
description: The HTTP status code
format: int32
example: 400
timestamp:
type: string
description: The timestamp when the error occurred
format: date-time
example: '2025-11-14T10:15:30.123Z'
BearerTokenErrorResponse:
type: object
properties:
error:
type: string
description: OAuth 2.0 error code
example: invalid_token
error_description:
type: string
description: Human-readable error description
example: An error occurred while attempting to decode the Jwt
description: OAuth 2.0 Bearer Token error response (RFC 6750)
securitySchemes:
apiKeyAuth:
description: 'API Key (format: vsp_sk_...)'
scheme: bearer
type: http
````