> ## Documentation Index > Fetch the complete documentation index at: https://docs.osaconnection.com/llms.txt > Use this file to discover all available pages before exploring further. # Check the service is up > Returns `200` when the API is accepting requests. It needs no key and returns no data, so it is safe for uptime monitors. ## OpenAPI ````yaml /openapi.yaml get /v1/health openapi: 3.1.0 info: title: OSA Partner API version: 1.0.0 summary: Send claims to adjusters in the OSA app and follow their acceptance. description: > The OSA Partner API lets an adjusting firm's claims system invite adjusters to the firm, send them claims, and see whether each claim was accepted or rejected in the OSA app. **Conventions** - All requests and responses are JSON (`application/json`); errors use RFC 9457 problem details (`application/problem+json`). - Field names are `snake_case`. Enum values are lowercase (for example `flood`, `pending_acceptance`), except US state and territory codes, which are the standard two-letter USPS codes, and flood zones, which are written as FEMA writes them (for example `AE`). - Enums are **open**: new values may be added to responses at any time, so your code must tolerate values it doesn't recognise. - Additive changes (new endpoints, new optional request fields, new response fields, new enum values) are made within `/v1`. Breaking changes go to a new version. - Requests are strict: an unknown or misspelled body field or query parameter is rejected with `422 validation_failed`, so typos can't be silently ignored. - Your own claim id (`external_id`) is stored on every claim and returned on every claim response, so you can match claims without keeping OSA's id. - Timestamps are RFC 3339 date-times in UTC. Dates that are calendar dates (such as the date of loss) are `YYYY-MM-DD` and are never converted between time zones. **Keys.** Every request except `GET /v1/health` needs an API key sent as `Authorization: Bearer `. Live keys start with `osa_live_`; test keys start with `osa_test_` and only reach test claims and test accounts. contact: name: OSA API support email: info@osaconnection.com url: https://docs.osaconnection.com servers: - url: https://api.osaconnection.com description: >- Production. Live and test keys both use this host; the key decides which data you reach. security: - apiKey: [] tags: - name: Claims description: > Send claims to adjusters, offer them to another adjuster, and poll for acceptance. `/v1/claims` is always the claims your firm sent through the API. - name: Adjusters description: Invite adjusters to your firm by their OSAID and track their invitations. - name: Account description: Check which firm and permissions your API key carries. - name: Health description: Service availability. No key needed. paths: /v1/health: get: tags: - Health summary: Check the service is up description: > Returns `200` when the API is accepting requests. It needs no key and returns no data, so it is safe for uptime monitors. operationId: getHealth responses: '200': description: The API is up. headers: X-Request-Id: $ref: '#/components/headers/RequestId' content: application/json: schema: $ref: '#/components/schemas/Health' examples: ok: summary: Healthy value: status: ok '500': $ref: '#/components/responses/InternalError' security: [] components: headers: RequestId: description: > The id of this request. Quote it to OSA support. On error responses it equals `request_id` in the body. required: true schema: type: string examples: request_id: summary: A request id value: 7f3e9a1c2b4d6e8f0a1b3c5d7e9f1a2b schemas: Health: type: object description: Service status. required: - status properties: status: type: string description: '`ok` when the API is accepting requests.' enum: - ok Problem: type: object description: > An RFC 9457 problem details object. Match on `code`, which is stable; `title` and `detail` are for people and may change. Quote `request_id` when contacting support. required: - type - title - status - detail - code - request_id properties: type: type: string format: uri description: A link to this error's documentation. title: type: string description: A short summary of the error. status: type: integer description: The HTTP status code. detail: type: string description: What went wrong in this request. code: type: string description: > The stable error code. `malformed_request` (400); `invalid_key` (401); `insufficient_scope`, `not_in_plan` (403); `not_found` (404); `duplicate_claim`, `claim_already_accepted`, `already_member`, `invitation_pending` (409); `payload_too_large` (413); `validation_failed`, `idempotency_key_reused`, `unknown_osaid`, `adjuster_not_in_firm`, `adjuster_not_accepting`, `environment_mismatch` (422); `rate_limited` (429); `internal_error` (500). New codes may be added. enum: - malformed_request - invalid_key - insufficient_scope - not_in_plan - not_found - duplicate_claim - claim_already_accepted - already_member - invitation_pending - payload_too_large - validation_failed - idempotency_key_reused - unknown_osaid - adjuster_not_in_firm - adjuster_not_accepting - environment_mismatch - rate_limited - internal_error request_id: type: string description: The id of this request. Quote it when contacting support. errors: type: array description: For `validation_failed`, each invalid field, parameter or header. items: type: object description: >- One problem. Exactly one of `pointer`, `parameter` or `header` says where. required: - detail properties: pointer: type: string description: >- JSON Pointer to a body field, for example `/loss/date`. Empty for the whole body. parameter: type: string description: The name of a query or path parameter, for example `limit`. header: type: string description: The name of a request header, for example `Idempotency-Key`. detail: type: string description: What is wrong with it. existing_claim_id: type: string format: uuid description: >- For `duplicate_claim`, the id of the claim that already exists. Always a claim your key can read. existing_claim_url: type: string format: uri description: >- For `duplicate_claim`, the API link to the claim that already exists. Always a claim your key can read. responses: InternalError: description: > Something failed on OSA's side (`internal_error`). Retry with exponential backoff; for `POST` requests, reuse the same `Idempotency-Key`. If it persists, contact OSA with the `request_id`. headers: X-Request-Id: $ref: '#/components/headers/RequestId' content: application/problem+json: schema: $ref: '#/components/schemas/Problem' examples: internal_error: summary: internal_error value: type: https://docs.osaconnection.com/errors#internal_error title: Internal error status: 500 detail: Something went wrong on our side. Retry later. code: internal_error request_id: 2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f securitySchemes: apiKey: type: http scheme: bearer bearerFormat: osa_live_… or osa_test_… description: > Send your API key as a bearer token: `Authorization: Bearer osa_live_…`. Keys are opaque; each belongs to exactly one firm and one purpose. Keys starting with `osa_test_` reach only test claims and test accounts. The scopes listed on each operation are the permissions the key needs; `GET /v1/me` shows the ones your key has. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.