> ## 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. # Get an OPS-scoped thruster by id > Retrieves a thruster resolved strictly by id within the OPERATIONS environment. Type is rendered UPPER_CASE (DT-17). Returns 404 if the id lives in a different environment (D-8 env-explicit lookup). ## OpenAPI ````yaml https://api.valar.space/api-docs/mintlify get /operations/spacecraft/{spacecraftId}/thrusters/{thrusterId} 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!

  1. 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.
  2. You can expand each method to get further information on the expected input parameters and the different responses that can be received.
  3. For both the input parameters and responses, an Example is present for clarification.
  4. For further details, the example snipped can be switched to Schema view, where a detailed explanation of each element can be found.
  5. 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.
  6. 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: >- Env-scoped thruster CRUD for the MISSION_ANALYSIS environment (EnvironmentFilter activates server-side via the /mission-analysis/ URL prefix). name: Mission Analysis Thrusters - description: >- Operations for managing state vectors — listing, importing, exporting, and deleting spacecraft state data name: State Vectors - description: >- Env-scoped spacecraft writes for the OPERATIONS environment (EnvironmentFilter activates server-side via the /operations/ URL prefix). name: Operations Spacecraft (write) - description: >- Env-scoped per-item payload (sensor) CRUD for the MISSION_ANALYSIS environment (EnvironmentFilter activates server-side via the /mission-analysis/ URL prefix). name: Mission Analysis Payloads - description: >- Env-scoped thruster CRUD for the OPERATIONS environment (EnvironmentFilter activates server-side via the /operations/ URL prefix). name: Operations Thrusters - description: >- Env-scoped spacecraft reads for the MISSION_ANALYSIS environment (EnvironmentFilter activates server-side via the /mission-analysis/ URL prefix). name: Mission Analysis Spacecraft - description: >- Env-scoped spacecraft reads for the OPERATIONS environment (EnvironmentFilter activates server-side via the /operations/ URL prefix). name: Operations Spacecraft - description: >- Env-scoped per-item payload (sensor) CRUD for the OPERATIONS environment (EnvironmentFilter activates server-side via the /operations/ URL prefix). name: Operations Payloads - description: >- Env-scoped spacecraft writes for the MISSION_ANALYSIS environment (EnvironmentFilter activates server-side via the /mission-analysis/ URL prefix). name: Mission Analysis Spacecraft (write) paths: /operations/spacecraft/{spacecraftId}/thrusters/{thrusterId}: get: tags: - Operations Thrusters summary: Get an OPS-scoped thruster by id description: >- Retrieves a thruster resolved strictly by id within the OPERATIONS environment. Type is rendered UPPER_CASE (DT-17). Returns 404 if the id lives in a different environment (D-8 env-explicit lookup). operationId: getOperationsThruster parameters: - description: Parent spacecraft id in: path name: spacecraftId required: true schema: type: string - description: Thruster id in: path name: thrusterId required: true schema: type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/EnvThrusterResponse' description: Thruster retrieved successfully '401': content: application/json: schema: $ref: '#/components/schemas/BearerTokenErrorResponse' description: Unauthorized - JWT token missing or invalid '403': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Forbidden - User lacks OPS env access or PERM_read:spacecraft permission '404': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Thruster not found in OPS scope security: - bearerAuth: [] components: schemas: EnvThrusterResponse: type: object properties: createdAt: type: string description: Timestamp when thruster was created format: date-time example: '2025-10-22T10:30:00Z' direction: type: string description: Thrust direction in 3D coordinate system example: Z+ enum: - X+ - X- - Y+ - Y- - Z+ - Z- id: type: string description: Thruster unique identifier (UUID) example: 550e8400-e29b-41d4-a716-446655440000 isp: type: number description: Specific impulse in seconds (s) format: double example: 300 maxBurnTime: type: number description: Maximum continuous burn duration in seconds (s) format: double example: 3600 name: type: string description: Thruster name (unique per spacecraft) example: Main Engine spacecraftId: type: string description: Spacecraft ID this thruster belongs to example: spacecraft-123 thrust: type: number description: Maximum thrust in Newtons (N) format: double example: 500 type: type: string description: >- Propulsion type (auto-computed from ISP), rendered UPPER_CASE per DT-17 example: CHEMICAL enum: - CHEMICAL - ELECTRIC updatedAt: type: string description: Timestamp when thruster was last updated format: date-time example: '2025-10-22T15:45:00Z' x: type: number description: Position X coordinate in meters (m) format: double example: 0 'y': type: number description: Position Y coordinate in meters (m) format: double example: 0 z: type: number description: Position Z coordinate in meters (m) format: double example: -1.5 description: Thruster response data 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) 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' securitySchemes: apiKeyAuth: description: 'API Key (format: vsp_sk_...)' scheme: bearer type: http ````