> ## 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.
# Upload measurement files
> Upload one or more measurement files for asynchronous processing. Supported formats: TDM (Tracking Data Message), SP3 (Standard Product 3), and OEM (Orbit Ephemeris Message). Each file is validated synchronously and then queued as a background job for full processing. The response includes per-file results with job IDs for tracking processing status.
## OpenAPI
````yaml https://api.valar.space/api-docs/mintlify post /operations/measurements
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/measurements:
post:
tags:
- Measurements
summary: Upload measurement files
description: >-
Upload one or more measurement files for asynchronous processing.
Supported formats: TDM (Tracking Data Message), SP3 (Standard Product
3), and OEM (Orbit Ephemeris Message). Each file is validated
synchronously and then queued as a background job for full processing.
The response includes per-file results with job IDs for tracking
processing status.
operationId: uploadMeasurementFiles
requestBody:
content:
multipart/form-data:
schema:
type: object
properties:
files:
type: array
description: Measurement files to upload (TDM, SP3, OEM formats)
items:
type: string
format: binary
required:
- files
responses:
'202':
content:
application/json:
schema:
$ref: '#/components/schemas/BatchUploadResponse'
description: Files accepted for processing
'207':
content:
application/json:
schema:
$ref: '#/components/schemas/BatchUploadResponse'
description: >-
Partial failure: at least one file failed; see results[] for
per-file outcomes
'400':
content:
application/json:
example:
timestamp: '2025-01-15T10:30:00.000Z'
status: 400
error: Bad Request
message: No files provided
path: /operations/measurements
schema:
$ref: '#/components/schemas/ErrorResponse'
description: No files provided or invalid request
'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/measurements
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Insufficient permissions
'413':
content:
application/json:
example:
timestamp: '2025-01-15T10:30:00.000Z'
status: 413
error: Payload Too Large
message: File size exceeds the maximum allowed limit
path: /operations/measurements
schema:
$ref: '#/components/schemas/ErrorResponse'
description: File size exceeds the maximum allowed limit
'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/measurements
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Internal server error
components:
schemas:
BatchUploadResponse:
type: object
properties:
failureCount:
type: integer
description: The number of files that failed to process
format: int32
example: 2
results:
type: array
description: Individual results for each file in the batch
items:
$ref: '#/components/schemas/FileUploadResult'
successCount:
type: integer
description: The number of successfully processed files
format: int32
example: 5
totalCount:
type: integer
description: The total number of files processed
format: int32
example: 7
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)
FileUploadResult:
type: object
properties:
errorCode:
type: string
description: The error code if the upload failed
nullable: true
example: TRK-4001
errors:
type: array
description: >-
List of per-block rejection details when status='error' came from a
partial ingest (DEV-3104). Null otherwise.
nullable: true
items:
$ref: '#/components/schemas/BlockRejectionDetail'
filename:
type: string
description: The name of the uploaded file
example: tracking_data_001.tdm
jobId:
type: string
description: The job ID for tracking async processing status
nullable: true
example: 550e8400-e29b-41d4-a716-446655440000
message:
type: string
description: A message describing the result
example: Successfully processed 150 measurements
status:
type: string
description: The status of the upload
example: success
enum:
- success
- error
description: Individual results for each file in the batch
BlockRejectionDetail:
type: object
properties:
blockId:
type: string
description: >-
Provider-supplied block identifier from the originating TDM, or a
synthetic "block-N" tag when the TDM omitted a SEG_ID. Null when the
rejected payload carries no block identifier at all.
nullable: true
example: block-1
code:
type: string
description: >-
DKR-2 §3.12 reject code (the TRK identifier from
TrackingFileErrorCode)
example: TRK-4006
firstEpoch:
type: string
description: >-
ISO-8601 UTC timestamp of the first rejected observation in the
block. Null when the rejected payload carries no observations (for
example a header-only block-fatal rejection such as TRK-4014
unsupported MODE).
nullable: true
example: '2026-04-27T01:14:29.9Z'
message:
type: string
description: >-
Localized rejection message, with the {0} placeholder substituted
from the IngestResult.Rejected.offendingValue() field when
applicable
example: 'Ambiguous Doppler correction state: YES'
description: >-
Per-block doppler rejection detail (DEV-3104, DKR-2 §3.12). One entry
per rejected block in the file's audit summary; populated only when
FileUploadResult.status equals "error" because of a
PartialIngestException.
nullable: true
securitySchemes:
apiKeyAuth:
description: 'API Key (format: vsp_sk_...)'
scheme: bearer
type: http
````