Bigcommerce

BigCommerce provides a comprehensive ecommerce API surface covering catalog management (products, categories, variants, modifiers), order processing, customer management, cart/checkout, and storefront rendering. For agents, the distinction between Management API (REST v3, server-side) and Storefront API (GraphQL, client-side) is important: agents handling backend operations (inventory updates, order processing, catalog enrichment) use the REST API, while agents generating storefront experiences use GraphQL. Multi-storefront support enables agents managing multiple brands from a single catalog. Headless commerce capabilities are strong — agents can build custom storefronts with full API-driven product and checkout flows. B2B features (company accounts, price lists, purchase orders) differentiate BigCommerce from Shopify for enterprise agents.

Management REST API at api.bigcommerce.com/stores/{store_hash}/v3/ covers products, orders, customers, carts, and settings. Product data model supports variants, custom fields, images, videos, and complex option sets. The Catalog API v3 is well-structured with consistent CRUD patterns. GraphQL Storefront API enables efficient frontend queries — product listings, search, and cart operations in typed, composable queries. Webhooks cover product, order, cart, and customer events with destination-based scoping. Pagination uses page-based and cursor-based patterns depending on endpoint. Batch operations via meta.pagination with limit/page. The dual API surface (REST for management, GraphQL for storefront) is conceptually clean but means agents need both integration patterns.

REST API errors return JSON with status, title, detail, and errors object for field-level validation. Standard HTTP status codes apply. Rate limits are generous on most plans: 150+ requests per 30-second window for most V3 endpoints, varies by plan. 429 responses include X-Rate-Limit-Requests-Left and X-Rate-Limit-Time-Reset-Ms headers for precise throttling. Webhook delivery retries with exponential backoff. Catalog operations with complex variant structures can timeout on large products — agents should batch variant updates. Order webhook events fire for each status transition. The error format is consistent and actionable across endpoints. API versioning (v2 → v3) is well-managed with clear migration guides.

Management API uses OAuth with API accounts — generating a set of credentials (access token, client ID, client secret) scoped to specific OAuth permission sets (products, orders, customers, etc.). This scoping is more granular than many ecommerce platforms. Single-click app installation uses OAuth authorization code flow for marketplace distribution. Storefront API tokens are created via the Management API and scoped to storefront-only access. V2 API used Basic Auth (deprecated path). For agents, creating a store-level API account with specific permissions is the standard approach — clean and appropriately scoped. No temporary credential mechanism. Token rotation requires creating new API accounts.

Developer documentation at developer.bigcommerce.com is well-organized with guides, API reference, and theme development docs. The API reference includes endpoint descriptions, parameter tables, and response examples. OpenAPI specs are available for client generation. GraphQL Storefront API has a dedicated explorer. The DevCenter organizes content by use case (catalog, orders, payments, multi-storefront) which helps agents find relevant patterns. SDKs: official Node client, community libraries for Python, Ruby, and PHP. The documentation explicitly addresses headless commerce patterns, which is valuable for agents building custom storefronts. Developer community and forums are active. BigCommerce partner ecosystem provides additional integration resources.