Data Sync & Integration

What Public API Does PayHelm Provide for BigCommerce Payments and Merchant Data?

Updated September 17, 2026
bigcommerce, api, mcp, public-api, payments, merchant-data, developers

What Public API Does PayHelm Provide for BigCommerce Payments and Merchant Data?

Short answer

PayHelm doesn't publish a separate "BigCommerce API." Instead, PayHelm syncs order, product, customer, and payment/financial-status data from your connected BigCommerce store, and exposes that data back out through one general-purpose public interface — a Model Context Protocol (MCP) server and its REST equivalent — that works the same way across every platform PayHelm connects to, BigCommerce included.

How the data flows

  1. You connect your BigCommerce store to PayHelm under Integrations → BigCommerce.
  2. PayHelm syncs orders, products, customers, and payment/financial-status details from BigCommerce's own API on a recurring schedule — this is PayHelm reading from BigCommerce, not a public API of PayHelm's.
  3. That synced data becomes queryable through PayHelm's own public MCP server / REST API, using a PayHelm API key — by you, your own app, or an AI coding agent you authorize.

The public interface

  • MCP endpoint: https://mcp.payhelm.com/mcp (Streamable HTTP/SSE, Authorization: Bearer <PAYHELM_API_KEY>)
  • REST equivalent: https://api.payhelm.com/v1 (same Bearer auth, JSON)
  • Full developer setup (Replit, Claude Code, Codex, GitHub Pages, curl examples): MCP developer docs
  • Machine-readable summaries for AI agents and crawlers: llms.txt and SKILL.md

Get your API key from the PayHelm dashboard under Settings → API Keys. Keys are scoped to your account — they only return data for stores and ad accounts you've connected.

BigCommerce-specific tools

These tools return data scoped to your connected BigCommerce store(s):

  • get_bigcommerce_orders — order records
  • get_bigcommerce_products — product catalog records
  • get_bigcommerce_customers — customer records
  • get_inventory_products — product-level inventory (stock, value, velocity, low-stock alerts)

Payments and merchant data across platforms

PayHelm doesn't expose a dedicated "payments" endpoint per platform. Payment and merchant detail is available as a dimension inside PayHelm's cross-platform reporting tools, which include your BigCommerce orders alongside every other connected store:

  • get_orders_report / get_charts_report — revenue, order count, and AOV broken out by payment method and financial status
  • get_customers_report — merchant-facing customer detail: total spend, order count, first/last order date, location
  • get_cross_platform_ads_performance — how ad spend correlates with BigCommerce revenue and conversions, alongside your other connected ad platforms

What's not included

  • No separate "payments object" API — no per-transaction card/processor-level detail beyond what BigCommerce itself reports through payment method and financial status.
  • No write-back to BigCommerce. Every BigCommerce tool listed above is read-only.
  • No access to data from stores you haven't connected — API keys are scoped to your account's connected platforms only.

Where to go next

Related Articles

Was this article helpful?

Still have questions? Our team is here to help.