> ## 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.
# Bulk mark or unmark measurements as outliers by source file
> Performs a bulk update of the outlier status on all measurements originating from a specific source file. File name matching is exact and case-sensitive. The returned count reflects all matching measurements updated within the current tenant.
## OpenAPI
````yaml https://api.valar.space/api-docs/mintlify patch /operations/measurements/outliers/by-file
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/outliers/by-file:
patch:
tags:
- Measurements
summary: Bulk mark or unmark measurements as outliers by source file
description: >-
Performs a bulk update of the outlier status on all measurements
originating from a specific source file. File name matching is exact and
case-sensitive. The returned count reflects all matching measurements
updated within the current tenant.
operationId: bulkMarkOutlierByFile
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/BulkMarkOutlierByFileRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BulkOutlierResponse'
description: Bulk operation completed successfully
'400':
content:
application/json:
example:
timestamp: '2025-01-15T10:30:00.000Z'
status: 400
error: Bad Request
message: Validation failed
path: /operations/measurements/outliers/by-file
fieldErrors:
fileName: must not be blank
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Invalid request — blank or invalid file name
'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/outliers/by-file
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Insufficient permissions — requires write:tracking authority
'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/outliers/by-file
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Internal server error
components:
schemas:
BulkMarkOutlierByFileRequest:
required:
- fileName
- isOutlier
type: object
properties:
fileName:
maxLength: 255
minLength: 0
pattern: ^[a-zA-Z0-9._\-\s]+$
type: string
description: >-
Source file name to match against measurements. Matching is exact
and case-sensitive.
example: tracking_data_2025-01-15.tdm
isOutlier:
type: boolean
description: >-
Whether to mark (true) or unmark (false) the measurements as
outliers
example: true
description: Request to bulk mark/unmark measurements as outliers by source file
BulkOutlierResponse:
type: object
properties:
updatedCount:
type: integer
description: Number of measurements successfully updated
format: int32
example: 42
description: Response for bulk outlier marking operations
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
````