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

AfterShip Courier connection API

The Courier connection API from AfterShip — 2 operation(s) for courier connection.

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

Requests are made against a single base URL, https://api.aftership.com/tracking/2026-07.

5 operations 2 paths 3 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.aftership.com/tracking/2026-07
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

AfterShip Courier connection API declares 1 security scheme for authenticating requests. An API key is passed in the header as as-api-key (as-api-key). By default, every request must be authenticated.

  • as-api-key — Legacy API keys with aftership-api-key headers are not supported anymore start from 2023-10 version. For more information, check [authentication](../../docs/qu…

Paths & Operations 5

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

Courier connection 5
GET
/courier-connections
Get courier connections
get-courier-connections 4 params → 200
POST
/courier-connections
Create courier connections
post-courier-connections body → 201
GET
/courier-connections/{id}
Get courier connection by id
get-courier-connections-by-id 1 param → 200
PATCH
/courier-connections/{id}
Update courier connection by id
put-courier-connections-by-id 1 param body → 200
DELETE
/courier-connections/{id}
Delete courier connection by id
delete-courier-connections-by-id 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Courier_connection (5 properties), Meta.v1 (3 properties), Courier_connection_response_get_multiple (2 properties). Each schema is shown below with its type and property counts.

Meta.v1
object
Meta data
3 properties 1 required
Courier_connection_response_get_multiple
object
Courier connection response for getting courier connections
2 properties 1 required
Courier_connection
object
This model represents user-created courier connection details. AfterShip will use this information to retrieve tracking updates from carriers based on the prov…
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aftership-courier-connection-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of AfterShip Courier connection 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.