Commerce API Overview
Overview
Section titled “Overview”The Corso Commerce API allows brands to create and manage claims through external systems rather than relying solely on the Corso customer portal or the Corso admin. This opens up new ways for customers to submit claims and for support teams to manage them directly from the tools they already use.
Common use cases include:
- CRM integrations — Support reps can submit claims on behalf of customers directly from tools like Salesforce or HubSpot without switching to the Corso admin
- Chat widgets and AI agents — Customers can submit claims through a live chat or AI-powered support experience without being redirected to the Corso customer portal
- Custom support flows — Brands can build tailored claim submission experiences that fit their support operations
When to Use the Commerce API
Section titled “When to Use the Commerce API”The Commerce API is a good fit when:
- You want customers to submit claims through a chat widget or AI agent rather than the Corso customer portal
- Your support team uses a CRM or helpdesk tool and needs to create or update claims without leaving that system
- You are building a custom support experience and need to connect it to Corso’s claims infrastructure
- You want to programmatically create, update, or sync claims between Corso and an external system
How the Commerce API Works
Section titled “How the Commerce API Works”The Commerce API allows your system to send claim and order data to Corso programmatically. Here is the typical workflow:
- A customer initiates a support interaction — through a chat widget, CRM, AI agent, or custom tool
- The customer provides their order details within that experience
- Your system sends the relevant data to Corso via the Commerce API
- Corso creates or updates the claim
- The claim is now visible and actionable within the Corso admin, just like any claim submitted through the customer portal
Data Managed Through the Commerce API
Section titled “Data Managed Through the Commerce API”Orders
Section titled “Orders”For Corso to process a claim, it needs to reference an existing order. If the order is not already in Corso (for example, if your brand is not on Shopify), order data can be sent through the API. This typically includes:
- Order ID
- Customer information
- Line items
- Pricing
- Shipping information
- Order date
Line Items
Section titled “Line Items”Line items represent the individual products within an order. Each line item typically contains:
- Product name
- SKU
- Quantity
- Price
- Product identifiers
Line item data allows Corso to determine which products are eligible for exchanges, warranties, registrations, and shipping protection coverage.
Fulfillments
Section titled “Fulfillments”Fulfillment data tells Corso when and how an order shipped. This typically includes:
- Shipment tracking number
- Carrier
- Shipment date
- Items included in the shipment
Fulfillment data enables shipment tracking, shipping protection claims, and delivery status monitoring within Corso.
Claims
Section titled “Claims”Claims are the core of what the Commerce API is built to support. A claim represents a customer issue related to an order, such as:
- A return or exchange request
- A warranty claim
- A lost, stolen, or damaged shipment
Claims can be created and updated through the Commerce API, keeping external systems synchronized with Corso throughout the claim lifecycle.
Shipping Claims
Section titled “Shipping Claims”Shipping claims relate specifically to shipping protection coverage. These may include lost packages, stolen deliveries, or damaged shipments. The Commerce API allows systems to submit and manage these claims programmatically without requiring the customer to use the Corso portal.
Registrations
Section titled “Registrations”Product registrations can also be submitted through the Commerce API, allowing customers to register products through any touchpoint rather than a dedicated registration page. Registration data may include:
- Proof of purchase
- Product information
- Purchase date
- Retailer where the item was purchased
Authentication
Section titled “Authentication”All requests to the Commerce API must be authenticated to ensure only authorized systems can send data to Corso. Authentication is handled using API credentials provided by the Corso team, which your backend system uses when making requests to the API.
Contact your Corso representative to obtain your API credentials.
Developer Documentation
Section titled “Developer Documentation”This article provides a high-level overview of the Commerce API. For detailed implementation instructions including API endpoints, request formats, response examples, and authentication setup, refer to the Corso Developer Documentation.