Big Cartel API: How to Build Integrations for SaaS Software

The Big Cartel API is a REST API that lets approved applications read and update data in Big Cartel stores. For SaaS developers, it is the technical entry point to a platform built for independent artists, makers, and small brands. However, Big Cartel limits app access, uses OAuth 2.0, and exposes a narrower set of operations than larger eCommerce platforms.

Therefore, teams that build order management, shipping, or catalog software should understand these constraints before they start. This guide explains how the Big Cartel API works, which resources it exposes, and what limits matter in practice. It also shows how API2Cart helps SaaS vendors add Big Cartel alongside other platforms through one unified API.

What Is the Big Cartel API?

The Big Cartel API, sometimes written as the BigCartel API, is the platform's official REST interface, currently at version 1. All endpoints start with https://api.bigcartel.com, and the version appears in every path, for example /v1/accounts/{account_id}. According to the Big Cartel API documentation, updates to V1 remain backward-compatible and appear in the API changelog.

Developers use the API to build apps for Big Cartel sellers. Typical examples include order import, shipment tracking, catalog management, and reporting tools. Requests and responses use the application/vnd.api+json media type, so most modern HTTP clients can work with it easily.

Big Cartel also supports webhooks and embeddable storefront scripts. As a result, an app can react to store events and extend the storefront without polling for every change.

How Big Cartel API Authentication Works

Big Cartel offers two authentication options. The right one depends on whether you build a public app or a private tool for your own store.

• OAuth 2.0 for apps. Third-party applications redirect the seller to Big Cartel to approve access. After approval, the app exchanges a temporary code for an access token. Then it sends that token in the Authorization: Bearer header.
• HTTP Basic authentication for personal projects. A seller can build a private integration for their own store with the store subdomain and password. Big Cartel states that this method is only for your own store.

Big Cartel approves a select number of partners to build apps. Consequently, a SaaS vendor that wants to serve many sellers should plan for an application and review process before launch.

Required Request Headers

Every request must include specific headers. Otherwise, the API rejects it:

• Accept: application/vnd.api+json on all requests.
• Content-Type: application/vnd.api+json on requests with a JSON body.
• User-Agent with your application name, version, and a contact URL or email. Without it, the API returns 400 Bad Request.

Most endpoints also require an account ID. You can get it from the Account API before you request orders or products.

Example: Retrieving Recent Orders with the Big Cartel API

The request below retrieves up to 20 orders updated since a given date, newest first. It uses the documented filter, sort, and page parameters.

curl -g "https://api.bigcartel.com/v1/accounts/ACCOUNT_ID/orders?filter[updated_at_from]=2026-10-01&sort=-updated_at&page[limit]=20" \
  -H "Accept: application/vnd.api+json" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "User-Agent: YourApp/1.0 (https://example.com/contact)"

List endpoints return 20 items by default. To get more results, use page[limit] and page[offset], or follow the pagination links in the response.

Big Cartel API Resources and Operations

The Big Cartel API documentation groups endpoints by resource. The table summarizes the resources most relevant to eCommerce SaaS products.

Note that product data includes options with their own price and quantity. However, the documented product update parameters cover fields such as name, description, status, and sale state. Therefore, check the documentation for each field you plan to write before you design a two-way sync.

Big Cartel Webhooks

Webhooks notify your application about changes in connected stores. They are available only to apps that use OAuth. All apps receive account.* webhooks by default. In contrast, order, cart, product, and shipment webhooks are approved per app, and some types require sellers on paid plans.

Key Benefits of Big Cartel API Integration

Big Cartel serves a specific audience. As a result, a well-built integration can deliver clear value to software vendors.

1. Access to a Focused Merchant Niche

Big Cartel sellers are often artists, designers, musicians, and small independent brands. Many of them run stores without in-house IT teams. Consequently, focused tools for order handling, shipping, or reporting can solve real problems for this segment.

2. Secure, Seller-Controlled Access

OAuth 2.0 lets sellers grant access without sharing passwords with your app. Sellers stay in control and can revoke access at any time. Your application then receives an account.deauthorized webhook, so it can stop processing that store.

3. Less Crowded App Ecosystem

Big Cartel approves a limited number of partner apps. For this reason, an approved app that solves a specific workflow can stand out more easily than on larger marketplaces.

Challenges and Limitations of the Big Cartel API

Before you commit to a direct integration, review the following constraints. Each one affects architecture and development effort.

1. App Approval and Plan Restrictions

Public apps need approval from Big Cartel, and webhook access is granted per app. In addition, some webhook types work only for sellers on paid plans. Therefore, your onboarding flow must handle stores that lack specific features.

2. Narrower Write Operations

The API focuses on core retail objects. For example, the documented product endpoints support listing, retrieving, updating, and repositioning products. As a result, workflows such as bulk catalog creation or detailed inventory management may need extra logic or a different approach.

3. Strict Request Requirements

Missing Accept or User-Agent headers cause failed requests. Similarly, most endpoints require the account ID. These details are simple, yet they often cause errors during the first integration tests.

4. Future Rate Limiting

The API does not currently limit the number of requests in a given period. However, Big Cartel states that rate limiting will be added in the future and asks developers to throttle requests responsibly. Consequently, design your sync jobs with backoff and incremental updates from the start.

5. Plan-Based Store Limits

Big Cartel plans include different feature limits. The documentation advises apps to read the account's plan through the Account API and respect those limits. For instance, an account may allow only a limited number of images per product.

How API2Cart Simplifies Big Cartel API Integration

Building and maintaining a direct Big Cartel integration requires OAuth handling, header management, data mapping, and monitoring of API changes. Moreover, most SaaS vendors build Big Cartel integrations alongside many other platforms. API2Cart addresses this with a single unified API for 80+ shopping platforms and marketplaces, including Big Cartel.

With Big Cartel integration via API2Cart, your software works with the same methods and data structures it uses for other connected platforms. To add a store, follow the guide on connecting Big Cartel to API2Cart.

Click here to accept Marketing cookies and load this content

API2Cart Methods Available for Big Cartel

The following methods are supported for Big Cartel according to the Big Cartel methods list:

• Products: product.list, product.info, product.count, and product.update for name, description, status, SEO URL, and sale state.
• Categories: category.list, category.info, and category.count.
• Orders: order.list, order.info, order.count, and order.fulfillment_status.list.
• Shipments: order.shipment.add, order.shipment.update, order.shipment.delete, order.shipment.list, and order.shipment.info.

Customer, product creation, and webhook methods are not currently available for Big Cartel through API2Cart. Therefore, plan customer-related features around the customer details included in orders.

Example: Importing Big Cartel Orders with order.list

The request below retrieves up to 20 Big Cartel orders modified since a given date. It uses API2Cart API v1.1 and parameters supported for Big Cartel.

curl -G "https://api.api2cart.com/v1.1/order.list.json" \
  -H "x-api-key: YOUR_API2CART_API_KEY" \
  -H "x-store-key: YOUR_BIG_CARTEL_STORE_KEY" \
  --data-urlencode "count=20" \
  --data-urlencode "modified_from=2026-10-01 00:00:00" \
  --data-urlencode "sort_by=modified_at" \
  --data-urlencode "response_fields={return_code,return_message,pagination,result{orders_count,order{order_id,create_at,status,totals,customer,shipping_address,order_products}}}"

The response uses the same structure for every supported platform. Below is a shortened example:

{
  "return_code": 0,
  "return_message": "",
  "pagination": {
    "previous": "",
    "next": "string"
  },
  "result": {
    "orders_count": 1,
    "order": [
      {
        "order_id": "string",
        "create_at": { "value": "string", "format": "string" },
        "status": { "id": "string", "name": "string" },
        "totals": { "total": 0, "subtotal": 0, "shipping": 0, "tax": 0, "discount": 0 },
        "customer": { "email": "string", "first_name": "string", "last_name": "string" },
        "shipping_address": { "address1": "string", "city": "string", "postcode": "string" },
        "order_products": [
          { "product_id": "string", "name": "string", "price": 0, "quantity": 0 }
        ]
      }
    ]
  }
}

A return_code of 0 means success. Meanwhile, pagination.next lets your application request the next page.

Use Cases for SaaS Vendors

• Order management systems import Big Cartel orders with order.list and track changes with modified_from.
• Shipping and fulfillment software adds tracking numbers back to orders with order.shipment.add. Learn more about Big Cartel shipping integration.
• ERP and accounting tools retrieve orders, totals, and product data for financial workflows.
• Catalog and PIM tools read products and categories, and update product names, descriptions, and status.

As a result, your team writes the integration logic once and reuses it for Big Cartel and other platforms. API2Cart also maintains the connection as platform APIs change.

Start your 14-day free API2Cart trial and test Big Cartel methods with your own development store.

Conclusion

The Big Cartel API gives approved apps secure access to orders, products, categories, shipments, and other store data. However, app approval, OAuth, strict headers, and limited write operations require careful planning.

For SaaS vendors that support many platforms, a unified API reduces this effort. API2Cart connects your software to Big Cartel and 80+ other eCommerce platforms through one integration. Consequently, your developers can spend more time on product features and less on maintaining separate connectors.

Ready to add Big Cartel to your software? Start your free 14-day trial and build your integration today.