Skip to main content

Account Endpoints

Use this page to find account-scoped metadata endpoints you typically call before building order/download automation.

This page lists endpoint intent only. Field-level contracts stay in the OpenAPI spec and endpoint-specific reference pages.

Before You Start​

  • Confirm authentication setup in Authentication.
  • Keep the OpenAPI spec nearby for exact request/response schema: https://api.clearsky.vision/api/specification.json.
  • Use endpoint reference pages and OpenAPI as the canonical source for field-level details.

Required headers:

x-api-key: <your-api-key>
Content-Type: application/json

Minimal Request Example​

Common metadata endpoint for model capability discovery:

curl -X GET "https://api.clearsky.vision/api/tasking/models" \
  -H "x-api-key: $CLEARSKY_API_KEY" \
  -H "Content-Type: application/json"

Other account-related controls are primarily handled in dashboard settings (key rotation and account controls). For API endpoint availability, use the OpenAPI spec as the source of truth.

Common Failure and Fix​

  • Failure: 401 or 403 when calling metadata endpoints.
  • Fix:
    • verify x-api-key,
    • rotate a revoked/expired key,
    • confirm request is sent to https://api.clearsky.vision.

If you receive 404, verify the endpoint path against the OpenAPI spec before retrying.

Next Step​