AfterShip Claims API

The Claims API from AfterShip — 10 operation(s) for claims.

Business capability
Post-Purchase AE-140.90

Operations 11

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /claims List shipping protection claims · Query claims #
Ask an LLM
“How do I see all claims filed against my shipping protection?”
“Can I list only the claims tied to one coverage?”
Tell an agent
List my claims.
Show claims filed under coverage {coverage_id}.
GET /claims/{id} Get a claim by its ID · Get a claim #
Ask an LLM
“Can I look up a claim using its ID from the claims list?”
“Where do I find a single claim's summary by ID?”
Tell an agent
Get claim {id}.
Look up claim {id} by ID.
GET /claims/{claim_id} Retrieve the full Claim resource · Get a claim #
Ask an LLM
“What does the full Claim resource show for a single claim?”
“How do I pull every detail of a claim, including items and status?”
Tell an agent
Retrieve the full Claim resource for {claim_id}.
Show all details, items and status of claim {claim_id}.
PATCH /claims/{claim_id} Update a claim's note, email or address · Update a claim #
Ask an LLM
“Can I change the contact email on a claim?”
“How do I fix the shipping address on an existing claim?”
Tell an agent
Set the contact email on claim {claim_id} to {contact_email}.
Add the note {note} to claim {claim_id}.
POST /claims/{claim_id}/approve Approve a claim under review · Approve a claim #
Ask an LLM
“How do I approve a claim that's still under review?”
“Can I leave an approval note and notify the customer when I accept a claim?”
Tell an agent
Approve claim {claim_id}.
Approve claim {claim_id} with the note {approval_note} and notify the customer.
POST /claims/{claim_id}/reject Reject a claim under review · Reject a claim #
Ask an LLM
“Can I decline a claim and give the customer a reason?”
“Is there a way to permanently reject a claim so it can't be resubmitted?”
Tell an agent destructive · confirm first
Reject claim {claim_id} because {reject_reason}.
Permanently reject claim {claim_id} with reason {reject_reason}.
POST /claims/{claim_id}/cancel Cancel an approved or in-process claim · Cancel a claim #
Ask an LLM
“How do I cancel a claim that was already approved?”
“Can I stop a claim that is in process and record why?”
Tell an agent destructive · confirm first
Cancel claim {claim_id} because {cancel_reason}.
Withdraw approved claim {claim_id} with the reason {cancel_reason}.
POST /claims/{claim_id}/resolve Mark an in-process claim as resolved · Resolve a claim #
Ask an LLM
“How do I close out a claim once it has been fully handled?”
“Can I resolve an in-process claim and let the customer know?”
Tell an agent
Resolve claim {claim_id} as completed.
Mark in-process claim {claim_id} resolved and notify the customer.
POST /claims/{claim_id}/receive Mark returned claim items as received · Mark claim as received #
Ask an LLM
“How do I record that the items returned for a claim have arrived?”
“Does marking claim items received change the claim's main status?”
Tell an agent
Mark the returned items for claim {claim_id} as received.
Record receipt of claim {claim_id}'s returned goods.
POST /claims/{claim_id}/match-resolution Check which resolutions a claim supports · Check claim resolution availability #
Ask an LLM
“Which resolution methods, like refund or reship, are available for this claim?”
“Which stores can be used to process a particular claim?”
Tell an agent
Check which resolution methods claim {claim_id} supports.
Find the stores that can process claim {claim_id}.
POST /claims/{claim_id}/process Process an approved claim's items · Process a claim #
Ask an LLM
“How do I process an approved claim once I've decided on the items?”
“What happens when I process a claim that's been approved?”
Tell an agent
Process approved claim {claim_id} for items {items}.
Move claim {claim_id} into processing with {items} and notify the customer.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/aftership:aftership-claims-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

aftership-claims-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Aftership Claims API
  contact:
    name: AfterShip Support
    url: https://www.aftership.com/contact-us
    email: support@aftership.com
  termsOfService: https://www.aftership.com/legal/terms-of-service
  version: '1.0'
  description: 'Operations tagged Claims across 2 of this provider''s published API definitions: aftership-protection-api-openapi.yml, aftership-warranty-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.aftership.com/admin/2022-01
  description: API Endpoint
- url: https://api.aftership.com/warranty/2026-07
  description: API Endpoint
tags:


# --- truncated at 32 KB (88 KB total) ---
# Full source: https://artifacts.apis.io/aftership/openapi/aftership-claims-api-openapi.yml