AfterShip
AfterShip is a post-purchase experience platform for ecommerce brands, retailers, marketplaces and 3PLs, founded in 2012 and headquartered in Hong Kong. Its products cover shipment tracking across 1,400+ carriers, branded tracking pages, AI-predicted estimated delivery dates, automated returns and exchanges, warranty and claims management, shipping-label generation and rate shopping (Postmen), shipment protection, address validation, AI email parsing, product personalization and discovery, and marketplace feed management. AfterShip publishes ten versioned, date-based REST APIs on api.aftership.com, each with a downloadable OpenAPI 3.1 description, seven first-party SDKs, webhooks, an OAuth 2.0 authorization server, and public and OAuth-gated MCP servers for AI agents.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles AfterShip the way a machine reads it — 45 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AfterShip scores 83.8/100 (exemplar), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from AfterShip's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aftership/"
title="AfterShip on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aftership.svg"
alt="AfterShip Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/aftership/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aftership/"
title="AfterShip on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aftership/card.svg"
alt="AfterShip Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile AfterShip
Each block below is one kind of artifact we hold for AfterShip. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 34
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AfterShip Address API
Address validation and correction so packages are delivered to a deliverable, normalized address.
AfterShip Address Validations (Beta) API
The Address Validations (Beta) API from AfterShip — 1 operation(s) for address validations (beta).
AfterShip Cancel Labels API
The Cancel Labels API from AfterShip — 2 operation(s) for cancel labels.
AfterShip Cancel Pickups API
The Cancel Pickups API from AfterShip — 2 operation(s) for cancel pickups.
AfterShip Claim Items API
Public endpoints for updating item-level claim data.
AfterShip Claim Shipments API
Public endpoints for creating and polling claim shipment resources.
AfterShip Claims API
The Claims API from AfterShip — 10 operation(s) for claims.
AfterShip Courier API
The Courier API from AfterShip — 2 operation(s) for courier.
AfterShip Courier connection API
The Courier connection API from AfterShip — 2 operation(s) for courier connection.
AfterShip Couriers API
The Couriers API from AfterShip — 1 operation(s) for couriers.
AfterShip Coverages API
The Coverages API from AfterShip — 5 operation(s) for coverages.
AfterShip Discoveries API
The Discoveries API from AfterShip — 4 operation(s) for discoveries.
AfterShip Email Parses API
The Email Parses API from AfterShip — 2 operation(s) for email parses.
AfterShip Estimated delivery date API
The Estimated delivery date API from AfterShip — 2 operation(s) for estimated delivery date.
AfterShip Fulfillments API
The Fulfillments API from AfterShip — 3 operation(s) for fulfillments.
AfterShip Item tags API
The Item tags API from AfterShip — 1 operation(s) for item tags.
AfterShip Labels API
The Labels API from AfterShip — 2 operation(s) for labels.
AfterShip Locations API
The Locations API from AfterShip — 2 operation(s) for locations.
AfterShip Manifests API
The Manifests API from AfterShip — 2 operation(s) for manifests.
AfterShip Memberships API
The Memberships API from AfterShip — 2 operation(s) for memberships.
AfterShip Orders API
The Orders API from AfterShip — 4 operation(s) for orders.
AfterShip Pickups API
The Pickups API from AfterShip — 2 operation(s) for pickups.
AfterShip Products API
The Products API from AfterShip — 4 operation(s) for products.
AfterShip Rates API
The Rates API from AfterShip — 2 operation(s) for rates.
AfterShip Return Dropoffs API
The Return Dropoffs API from AfterShip — 1 operation(s) for return dropoffs.
AfterShip Return items API
The Return items API from AfterShip — 2 operation(s) for return items.
AfterShip Returns API
Create, approve, reject, resolve and receive returns by return ID or RMA number, manage return items, item tags and returns-page deep links.
AfterShip Returns Page API
The Returns Page API from AfterShip — 1 operation(s) for returns page.
AfterShip Roles API
The Roles API from AfterShip — 1 operation(s) for roles.
AfterShip Shipper Accounts API
The Shipper Accounts API from AfterShip — 5 operation(s) for shipper accounts.
AfterShip Specific Shipper Accounts API
The Specific Shipper Accounts API from AfterShip — 2 operation(s) for specific shipper accounts.
AfterShip Stores API
The Stores API from AfterShip — 2 operation(s) for stores.
AfterShip Tracking API
Shipment tracking across 1,400+ carriers: create and query trackings, detect couriers, manage courier connections, and predict estimated delivery dates.
AfterShip Warranty Registrations API
Public endpoints for querying and correcting warranty registration data.
Scroll within the panel for all 34 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
AfterShip Tracking & Returns MCP Server
AfterShip publishes an anonymous, no-auth remote MCP server for real-time package tracking and a Returns Center demo, plus two OAuth-gated remote MCP servers (Post-purchase and ...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aftership Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Aftership Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Aftership Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for AfterShip — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 6
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aftership · machine-readable index on apis.io
This is an independent, third-party profile of AfterShip, 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.