Skip to main content

How Do You Find Your Store Hash and Create an API Access Token in BigCommerce

Easily connect your BigCommerce store to Endlss by locating your store hash and generating a secure API access token.

Updated in the last hour

Why you need this

To integrate your BigCommerce store with Endlss, you’ll need your Store Hash and a V2/V3 API Access Token. These allow us to sync your products, orders, and customer data securely and efficiently.


How to Find Your Store Hash and Create an API Access Token

  1. Log into your BigCommerce admin
    Go to Log In – BigCommerce and enter your credentials.

  2. Go to API settings
    In the left-hand menu, scroll to Settings and select Store-level API Accounts.

  3. Create a new API account

    • Select Create API Account

    • Give your API a recognizable name (e.g., “Endlss Integration”)

    • Ensure Token Type is set to V2/V3 API Token

  4. Set the OAuth Scopes
    Use the following permissions for proper integration with Endlss:

    • Checkout Content: modify

    • Customers: read-only

    • Information & Settings: read-only

    • Orders: modify

    • Products: read-only

    • Carts: modify

    • Checkouts: modify

  5. Save and collect your credentials
    Once saved, BigCommerce will display your:

    • Client ID

    • Client Secret

    • Access Token

    You’ll only need the Client ID and Access Token for Endlss.


🔥 Hot Tip 🔥

Copy your credentials somewhere safe—BigCommerce won’t show the Access Token again once you close the window.


What is the Store Hash?

Your Store Hash is part of your BigCommerce API URL and looks like this:
https://api.bigcommerce.com/stores/**abc123**/v3/
In this example, abc123 is the store hash.


Need help?

If you're stuck, reach out to your Endlss onboarding team.

Check out the Endlss resource library for best practices and inspiration on succeeding with influencer programs on Endlss.


The product images shown are for illustration purposes only and may not be an exact representation of the product.

Did this answer your question?