Token Access Explained
A token is like a secret key that belongs only to you.
When you download feeds from your account portal (for example, the inventory or product XML), the system needs to confirm your identity. Instead of asking for your password every time, it includes your secret key (the token) inside the download link.
Think of it like this:
- You have a secret door (your download link).
- The door only opens if your secret key (the token) is included in the link.
- The key is unique, no one else has the same one.
So when you open your inventory XML feed, the link looks something like this:
https://app.scala-nl.com/8653572931913/d43ae488-36c6-4224-8cab-d77be094cc49/xml_inventory.xml
- 8653572931913 = your customer number (automatically generated and not changeable)
- d43ae488-36c6-4224-8cab-d77be094cc49 = your token
This confirms: “This person is allowed to see this.”
Your product XML feed looks like this:
https://app.scala-nl.com/8653572931913/d43ae488-36c6-4224-8cab-d77be094cc49/webservice/channel/en/xml
- 8653572931913 = website customer code
- d43ae488-36c6-4224-8cab-d77be094cc49 = token
- en = language
Please note: This is an example. Your customer number and token are unique to you. The customer number cannot change, but you can refresh your token at any time.
If you think someone else might have access to your feeds, refresh your token. A new token will be generated instantly, the old one will stop working immediately, and your account portal will automatically update the new links. If your website or system is connected to these feeds, don’t forget to update your token there as well.
In short:
- Token = secret key
- URL = your personal link with your secret key in it
- Refreshing your token = changing your key for safety