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 Delivery Config API

The DeliveryConfig API from Umbra — 3 operation(s) for deliveryconfig.

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

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

This API exposes 4 operations across 3 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 5.1.0.

Requests are made against a single base URL, https://api.canopy.umbra.space/delivery.

4 operations 3 paths 11 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

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

Paths & Operations 4

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

DeliveryConfig 4
GET
/delivery-config/
List Delivery Configs
list_delivery_configs → 200422
POST
/delivery-config/
Post Delivery Config
post_delivery_config body → 201422
DELETE
/delivery-config/{delivery_config_id}
Delete Delivery Config
delete_delivery_config 1 param → 200422
POST
/delivery-config/{delivery_config_id}/verify
Verify Delivery Config
verify_delivery_config 1 param → 200422

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are DeliveryConfigResponse (12 properties), ValidationError (5 properties), DeliveryConfigRequest (5 properties), S3UmbraRoleOptions (5 properties). Each schema is shown below with its type and property counts.

DeliveryConfigResponse
object
Public view of delivery configs returned by all /delivery-config routes
12 properties 12 required
JsonValue
DeliveryConfigListResponse
object
1 property 1 required
HTTPValidationError
object
1 property
S3UmbraRoleOptions
object
Deliver data to S3 using Umbra's data delivery IAM Role
5 properties 2 required
GCSWIFOptions
object
Config used to deliver data using Umbra's data delivery IAM Role to a GCS bucket via WIF.
5 properties 3 required
PackagingOption
string
Specifies packaging options available to specify on a delivery config.
FileNamingConvention
string
Controls which file naming convention to use during delivery.
DeliveryConfigRequest
object
Body of POST /delivery-config
5 properties 2 required
ValidationError
object
5 properties 3 required
DeliveryConfigStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

umbra-deliveryconfig-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 Feasibility 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 Delivery Config 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.