Access tokens are useful in token-based authentication to allow access to static assets or dynamic documents. Shortly, we will introduce two types of tokens:
Further, the Icecat team checks if the usage of tokens conforms to the subscriptions of a user. Additionally, the team will monitor suspicious tokens and revoke tokens, if necessary.
Furthermore, Icecat supports backward compatibility. So, we still process those calls made without tokens as usual by comparing the IP address of the request to IPs in a whitelist. In contrast, calls with Access Tokens will not be validated by checking the IP address against the whitelist. Therefore, no additional configuration is required for existing client implementations.
A new access page on Icecat.biz will go live in February 2022. After that, authorized users will be able to generate for themselves the two types of tokens on the access page, without the need for contacting support. Furthermore, we will revoke unnecessary or compromised tokens via the same page. Moreover, users can create as many tokens of each type as is necessary for their applications.
Here an example of the use of an API Access Token:
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?product_id={product_id};lang={short_code};output=productxml' \ --header 'Api-Token: {your_api_token}'
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?lang={langcode}&prod_id={mpn}&vendor={brandName}&output=productxml' \ --header 'Api-Token: {your_api_token}'
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?ean_upc={gtin}&lang={langcode}&output=productxml' \ --header 'Api-Token: {your_api_token}'
Of course, you get an error if you send a non-existing or revoked API token to Icecat.
Here an example of the use of a Content Access Token:
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?product_id={product_id};lang={short_code};output=productxml' \ --header 'Content-Token: {your_content_token}'
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?lang={langcode}&prod_id={mpn}&vendor={brandName}&output=productxml' \ --header 'Content-Token: {your_content_token}'
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?ean_upc={gtin}&lang={langcode}&output=productxml' \ --header 'Content-Token: {your_content_token}'
In case you send a Content token, we will add the token to all content galleries, multimedia objects, and reasons to buy. Below, a code example:
https://icecat.com/objects/1234567890.mp4?content_token={your_content_token}
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?product_id={product_id};lang={short_code};output=productxml' \ --header 'Api-Token: {your_api_token}' \ --header 'Content-Token: {your_content_token}'
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?lang={langcode}&prod_id={mpn}&vendor={brandName}&output=productxml' \ --header 'Api-Token: {your_api_token}' \ --header 'Content-Token: {your_content_token}'
curl --location --request GET 'https://data.icecat.biz/xml_s3/xml_server3.cgi?ean_upc={gtin}&lang={langcode}&output=productxml' \ --header 'Api-Token: {your_api_token}' \ --header 'Content-Token: {your_content_token}'
Don’t hesitate to get in touch with support to receive your access tokens and to revoke them when needed.
Read further: News, API acces tokens, content access tokens, tokens
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Δ