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

Airspace Technologies Orders API

We support order creation, updates, cancellation, information, and document upload.

Airspace Technologies Orders API is one of 6 APIs that Airspace Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against a single base URL, https://{environment}.airspace.com/api/public/v2.

15 operations 12 paths 16 schemas 1 DELETE5 GET3 PATCH4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.6.2
Base URL
https://api.airspace.com/api/public/v3
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Airspace Technologies Orders API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer).

  • Bearer — Unique API key necessary to make API requests.

Paths & Operations 15

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

Orders 15

We support order creation, updates, cancellation, information, and document upload.

GET
/orders
List Orders
getOrders 13 params → 200401
POST
/orders
Create an Order
createOrder body → 201401422
GET
/orders/{tracking_id}
Retrieve an Order
getOrderById 2 params → 200401404
PATCH
/orders/{tracking_id}
Update an Order
updateOrder 1 param body → 200401409422404
DELETE
/orders/{tracking_id}
Cancel an Order
deleteOrder 2 params → 200202401409404
POST
/orders/{tracking_id}/documents
Add documents to an Order
uploadDocument 1 param body → 200409422
PATCH
/orders/{tracking_id}/activate_will_call
Activate a will call Order
activateWillCall 1 param body → 200409404
GET
/orders/events
Events for Orders
getOrdersEvents 13 params → 200401
GET
/orders/{tracking_id}/events
Retrieve an Order's events
getEventsForOrderById 2 params → 200401404
PUT
/orders/{tracking_id}/activate
Activate an Order
activateOrder 1 param body → 202404
PUT
/orders/{tracking_id}/test_order_progression
Test progress an Order
testProgressOrder 1 param body → 200404
POST
/orders/quotes
Create a Quote
createQuote body → 202422
GET
/orders/quotes/{tracking_id}
Retrieve a Quote
getQuote 1 param → 200401
POST
/orders/will_call
Create a will call Order
createWillCallOrder body → 202422
PATCH
/orders/will_call/{tracking_id}
Update a will call Order
updateWillCallOrder 1 param body → 202401404422

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are order (14 properties), piece_2 (12 properties), delivery_address (12 properties), piece (12 properties). Each schema is shown below with its type and property counts.

geofence_miles_delivery
object
1 property
piece
object
12 properties 7 required
reference
object
2 properties 1 required
geofence_miles_pickup
object
1 property
email_notification
upid
object
An identifier specified on the package to verify we are picking up the correct piece when an Airspace label is not used.
2 properties 2 required
order
object
14 properties 4 required
pickup_address_2
object
Pickup address for order
12 properties 4 required
pickup_time
string
Send a value in this key only if you want to specify a pickup time. - For future orders, the value should be at least two hours in the future (in the timezone…
delivery_address
object
Delivery address for order
12 properties 4 required
shipment_viability
object
Viability window for a shipment. This is the time period for which the shipment is viable and we best ensure for it to be delivered prior to its expiration. Th…
2 properties 1 required
contact
object
Location contact
3 properties 2 required
custom_attributes
object
6 properties 1 required
destination_address
object
Destination address for order
11 properties 4 required
pickup_address
object
Pickup address for order
11 properties 4 required
piece_2
object
12 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

airspace-technologies-orders-api-openapi.yml Raw ↑

Other APIs Airspace Technologies publishes across the network.

Airspace Technologies Address Books API
Airspace Technologies Invoices API
Airspace Technologies Labels API
Airspace Technologies Piece Libraries API
Airspace Technologies Quotes API
Where this information came from

This is an independent, third-party profile of Airspace Technologies Orders 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.