Legacy API keys

Hello, I recently purchased a plugin. When I go to the api page, there are only options for generating a “legacy” key. The instruction do not mention anything about legacy. Do I use this key or is there something not working correctly for me?



Hi @OTEFAdmin,

If the plugin has been updated in the last few years, it’s probably asking for a “personal token” from the new Build API. You can generate a personal token at the following URL. I’ve pre-selected many of the commonly required permissions for you.


If that doesn’t work, let me know exactly what you’re trying to do (i.e. are you attempting to enable automatic updates or something else?) and provide the name of the plugin if possible.


1 Like