How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Umbra Feasibility API

The Feasibility API from Umbra — 2 operation(s) for feasibility.

Umbra Feasibility API is one of 15 APIs that Umbra publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Feasibility. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 3.13.0.

Requests are made against 2 base URLs: https://api.canopy.umbra.space/tasking, https://api.canopy.prod.umbra-sandbox.space/tasking.

2 operations 2 paths 16 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.13.0
Base URL
https://api.canopy.umbra.space/tasking
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Umbra Feasibility API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Feasibility 2
POST
/feasibilities
Create Feasibility
create_feasibility body → 201422
GET
/feasibilities/{id}
Get Feasibility
get_feasibility 1 param → 200422

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Opportunity (16 properties), SpotlightConstraints (10 properties), Feasibility (8 properties), ScanConstraints (7 properties). Each schema is shown below with its type and property counts.

Point
object
Point Model
3 properties 2 required
FeasibilityStatus
string
Feasibility Status
HTTPValidationError
object
1 property
ScanConstraints
object
7 properties 1 required
FeasibilityRequest-Output
object
7 properties 6 required
FeasibilityRequest-Input
object
7 properties 3 required
Feasibility
object
An async operation that checks the active schedule and returns Opportunities Feasibility begins in the RECEIVED state and transitions to COMPLETE if the Umbra…
8 properties 2 required
Position2D
array
LineString
object
LineString Model
3 properties 2 required
PolarizationEnum
string
The first letter indicates the orientation of the wave as it is transmitted. The second letter indicates how the wave is filtered when received.
ImagingMode
string
The Imaging Mode for the Task
ValidationError
object
5 properties 3 required
Position3D
array
Opportunity
object
An open window on the active schedule that satisfies the given Feasibility constraints For more information about the geometry fields, see: https://docs.canopy…
16 properties 13 required
SceneSize
string
The requested Spotlight Scene Size in kilometers.
SpotlightConstraints
object
10 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

umbra-feasibility-api-openapi.yml Raw ↑

Other APIs Umbra publishes across the network.

Umbra Canopy Documentation MCP Server
Umbra Client Credentials API
Umbra Collections API
Umbra Collect Metadata API
Umbra Collects API
Umbra Delivery Config API
Umbra Organizations API
Umbra Preview API
Umbra Preview Image API
Umbra Product Constraints API
Umbra Restricted Access Areas API
Umbra Search API
Where this information came from

This is an independent, third-party profile of Umbra Feasibility API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.