E2C Store API

Read your store's orders, products, customers, and reports from your own scripts, spreadsheets, and tools like Zapier.

API docs: Introduction

Overview

The E2C Store API gives you access to your own store's data over HTTPS, returned as JSON. Use it to pull new orders into a spreadsheet, sync stock and prices with another system, add products from your inventory tool, or trigger a Zapier workflow when a sale comes in.

Most endpoints are GET requests that only read. Products and categories can also be created and edited, with keys that have the matching :write permission; see writing data. Nothing in the API deletes. All endpoints live under one base URL:

Base URL
https://e2c.store/api/v1/

Where to go next

Quick start

  1. In your dashboard, go to Settings → API keys and create a key. Choose only the permissions you need. Only the store owner can create keys.
  2. Copy the key. It's shown once, so store it somewhere safe, like a password manager or your tool's secret settings.
  3. Send the key as a Bearer token. This call returns your store's details and works with any key:
Request
export E2C_API_KEY="e2c_sk_your_key_here"

curl "https://e2c.store/api/v1/store" \
  -H "Authorization: Bearer $E2C_API_KEY"
Response
{
  "data": {
    "name": "Maple & Thread",
    "currency": "CAD",
    "timezone": "America/Toronto",
    "api_key": { "scopes": ["orders:read", "products:read"] }
  }
}

In Zapier, use a Webhooks by Zapier GET step or an API Request action with the same URL and Authorization header.

Authentication

Every request needs an Authorization: Bearer <key> header. Keys start with e2c_sk_.

Keys sent in the URL are rejected, because URLs end up in server and browser logs. Treat a key like a password. If one leaks, revoke it in Settings → API keys and create a new one. Revoking takes effect immediately.

Permissions

Each key carries one or more permissions. An endpoint that needs a permission the key doesn't have returns 403 insufficient_scope. Reading categories and reviews needs any one of products:read, services:read, or events:read. Write permissions don't include read access, so give a key both when it needs to look things up too.

PermissionGrants
orders:readOrders, items, shipping, and tracking, including the buyer's name and shipping address.
products:readPhysical and digital products, variants, stock, and their reviews.
services:readServices and their reviews.
events:readEvents, ticket types and sales, and their reviews.
customers:readThe customer list. Also adds the buyer's email and phone to order responses.
reports:readSales, revenue trend, order status, top products, and traffic reports.
categories:writeCreate categories, and rename, recode, show, or hide them.
products:writeCreate physical products, and edit the details, price, stock, and visibility of physical and digital products.