Access tokens are useful in token-based authentication to allow access to static assets or dynamic documents. We have two types of tokens:
API Access Token is useful to access XML and JSON files.
–header ‘Api-Token: ………
Content Access Tokens are useful to access static resources like images, videos, and any other supported types of media objects.
–header ‘Content-Token: ………
?content_token=………
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.
Icecat also offers app_key service to Full Icecat users who are willing to download content in JSON format.
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.
Icecat users can get Access Tokens and app_key from the Icecat portal on “My Profile”. Please note app_key is available only for Full Icecat users.
Furthermore, we will revoke unnecessary or compromised tokens via the same page. Moreover, users can create as many Access Tokens of each type as is necessary for their applications.
Here is 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 at the end of the URL:
https://icecat.com/objects/1234567890.mp4?content_token={your_content_token}
In case you send a Content token together with API token, we will add the Content token to all media asset URLs. Below, is a code example:
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}'
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
Δ