August 27, 2026: The Commerce API is now available for managing stores, catalogs, orders, and taxes

You can now manage a GoDaddy commerce store programmatically — configuration, catalog, orders, customers, taxes, and payment records — so you can run a store from your own code.

What changed

Commerce endpoints are available across REST and GraphQL subgraphs. Each authenticates with a Personal Access Token holding the matching commerce.* scope:

• Stores and sales channels (REST) — read a store and its attributes with commerce.store:read; list the channels a customer can buy from with commerce.channel:read.
• Catalog — POST /v2/commerce/stores/{storeId}/catalog-subgraph. Create and manage SKUs and SKU groups with commerce.product:read and commerce.product:write.
• Orders — POST /v1/commerce/order-subgraph. Take an order from DRAFT to OPEN to COMPLETED or CANCELED with commerce.order:read, :create, :update, :complete, and :cancel.
• Customers (REST) — list, read, create, and update customer records with commerce.customer:read, :create, and :update. Creating a customer de-duplicates against existing channel data instead of adding a second record.
• Transactions (REST) — read the authorizations, captures, sales, and refunds behind an order with commerce.transaction:read, so you can reconcile what was sold against what was paid.
• Taxes — POST /v2/commerce/stores/{storeId}/tax-subgraph. Create, update, and delete tax rates with commerce.tax:read, :create, :write, and :delete.

Who is affected

Available to developers with a GoDaddy account and an active commerce store. These are new endpoints on a new surface: no existing Domains, Auctions, or hosting integration is affected, and no action is required.

Links

• About the Commerce API — structure, authentication models, and how the entities relate
• Commerce API scopes — the scope-to-endpoint mapping
• Personal Access Tokens — how to create a token and grant scopes

Last updated on