> ## 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.
# Export stored maneuvers
> Select IDs using exactly one spacecraftIds value and 1–100 maneuverIds, without time bounds; or select a range using 1–50 spacecraftIds and both startDate and endDate, without maneuverIds. endDate must be after startDate. spacecraftIds accepts repeated or comma-separated parameters. maneuverIds accepts repeated parameters only; commas are literal identity characters. Duplicate maneuverIds are invalid. One selected ID returns OCM; multiple IDs return ZIP. Range exports return OCM for one spacecraft and ZIP for multiple spacecraft. No request body is used.
## OpenAPI
````yaml https://api.valar.space/api-docs/mintlify get /operations/maneuvers/export
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, select
Authorize and enter your API key. The key is sent as a bearer token
in the
Authorization header.
title: API Documentation
version: 1.0.0
servers:
- url: https://api.valar.space
description: VALAR API Server
- 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
- description: Register, list, read, update, and manage the lifecycle of your spacecraft.
name: Spacecraft
- description: Manage the thrusters mounted on a spacecraft.
name: Thrusters
- description: Manage the payloads (sensors) mounted on a spacecraft.
name: Payloads
- description: >-
Maneuver API 2.0.0: create, read, edit, delete, import, and export
spacecraft maneuvers.
name: Maneuvers
paths:
/operations/maneuvers/export:
get:
tags:
- Maneuvers
summary: Export stored maneuvers
description: >-
Select IDs using exactly one spacecraftIds value and 1–100 maneuverIds,
without time bounds; or select a range using 1–50 spacecraftIds and both
startDate and endDate, without maneuverIds. endDate must be after
startDate. spacecraftIds accepts repeated or comma-separated parameters.
maneuverIds accepts repeated parameters only; commas are literal
identity characters. Duplicate maneuverIds are invalid. One selected ID
returns OCM; multiple IDs return ZIP. Range exports return OCM for one
spacecraft and ZIP for multiple spacecraft. No request body is used.
operationId: exportOperationsManeuvers
parameters:
- description: VALAR spacecraft IDs; repeated or comma-separated
in: query
name: spacecraftIds
required: true
schema:
maxItems: 50
minItems: 1
type: array
items:
type: string
- description: >-
Stable maneuver IDs scoped to one spacecraft; repeat this parameter
for each ID. Commas, spaces and Unicode are literal identity
characters, not delimiters. Duplicate IDs are invalid.
explode: true
in: query
name: maneuverIds
required: false
schema:
maxItems: 100
minItems: 1
uniqueItems: true
type: array
items:
maxLength: 63
type: string
style: form
- in: query
name: startDate
required: false
schema:
type: string
format: date-time
- in: query
name: endDate
required: false
schema:
type: string
format: date-time
responses:
'200':
content:
application/zip:
schema:
type: string
format: byte
text/plain:
schema:
type: string
format: byte
description: OCM text or ZIP of OCMs
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Invalid or ambiguous export selection
security:
- apiKeyAuth: []
components:
schemas:
ErrorResponse:
type: object
properties:
code:
type: string
description: Stable frontend-dictionary error code
nullable: true
example: import.tracking.tdm.parse_failed
correlationId:
type: string
description: Server-generated opaque identifier for support correlation
nullable: true
example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
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: The HTTP status reason phrase or exception-handler code
example: Bad Request
fieldErrors:
type: object
additionalProperties:
type: string
description: Field-level validation errors (field name to error message)
description: Field-level validation errors (field name to error message)
message:
type: string
description: Detailed error message
example: Invalid spacecraft ID format
params:
type: object
additionalProperties:
type: string
description: Per-key allowlisted structured params for frontend rendering
nullable: true
description: Per-key allowlisted structured params for frontend rendering
nullable: true
path:
type: string
description: The request path where the error occurred
example: /api/v1/stm/credentials
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'
description: Standard API error response
securitySchemes:
apiKeyAuth:
description: 'API Key (format: vsp_sk_...)'
scheme: bearer
type: http
````