Authentication

Your client ID and client secret cannot call the API themselves. They are the credentials for an OAuth 2.0 authorization-code grant, which issues the access token you call with.

What you’ll build

An OAuth flow that gets one access token per Zentail seller, and a first call made with that token.

Before you start

• You hold a client ID and client secret from application registration.

1. Get a token for each seller

Build the exchange from Zentail authentication flow. That page is the one description of the flow for every Zentail integration: the redirect, the authorization code and the token request.

Each seller that sells on your channel gets its own token. Store it against that seller’s account on your channel.

Caution

A token belongs to one Zentail seller account. Use it only for requests made on that seller’s behalf.

2. Make a first call

Send the token as the whole Authorization header value, with no Bearer prefix. GET /v2/storefront/taxonomy/product_type is a safe first call. It is read-only, takes no parameters, and belongs to the next step:

curl "https://api.zentail.com/v2/storefront/taxonomy/product_type" \
  -H "Authorization: v2podKNZ395VqsQ7dz0afA1T9HpfPQkvoJHHo3Vow4U=" \
  -H "accept: application/json"

The response lists, under productTypes, the product types you have created so far.

Legacy (v1)

v1 routes take the same token in the same Authorization header.

Next steps

Send us your taxonomy data, so we can begin mapping it.