There are two type of URI to use while you are developing apps, the base API url that you will use to consume different type of resources like (orders, products, coupons), the other URI is the base of OAuth2.0 server, which you will use to get your app authenticated on a merchant store as explained in here.
Base API URL
Base OAuth server URL
There are two types of token, each of your requests must send along other payloads
Authorization token can be generated directly through our oAuth2.0 server (once a merchant install your application, you will get this token via the callback method), this token will be used to in your outgoing request as authorization header, here is a sample cURL with access token
Once you are subscribed to a backend, you can now generate either Production keys or Sandbox Keys.
Some backend require Admin approval on production keys generation.
Unlike the authorization token, the X-Manager-Token can be generated through your store admin panel and via the oAuth2.0 server, this token is used to identify your store to our backend, to generate this token manually you can follow these simple steps:
From your store settings → integrations → Zid, or click here.
Now you can generate your X-Manager-Token
Note that some of endpoints does not require X-Manager-Token, however, the authorization token is a must in every single request, to get a better clue, always use Try It feature from our partner dashboard.
Playing with APIs
You can play with all of our APIs endpoints, moreover, all of our apis have a fully documented JSON schema to referee to while building applications, to try out the API, you will need to register your account in the partner dashboard then create your development store, finally you can try out any endpoint from the TryIt tab