Access forbidden

Created: 1304242870|%e %B %Y, %H:%M|agohover by leiger, Last updated: 1305775066|%O ago by Rolandius. History

TODO - This page needs to be re-written to be clearer! At the moment it's just a bunch of disorganised facts all over the place.

The access forbidden error message appears when you have a valid API key entered into STE, but the site you are trying to access has not enabled API settings for it's members.

Each Wikidot user now has a read-only & read-write key – Pro users automatically, Free users upon request (more info on this further down the page).

To import (read) a page using STE, you must:

  • Have a valid API key.
  • Enter the valid read-only OR read-write key into STE.
  • Be a member of the site.
  • Have API permissions to read from site within site manager.
  • Have regular permissions to read page i.e. not private category.

To export (write) a page using STE, you must:

  • Have a valid API key.
  • Enter the valid read-write key into STE (read-only keys don't allow exporting/editing of sites).
  • Be a member of the site.
  • Have API permissions set to write to the site within site manager.
  • Have regular permissions to write (edit) the page.

Warning/note: By default, no one in your site has API permissions. (Not even the master administrator!) Therefore, the API settings need to be manually enabled for each and every site you want to read from or write to using STE.

If you entered an API key into STE before this update took effect, you need to generate a new API key in your user account settings on Wikidot.com, and then enter the new key into STE before anything will work.

All Pro Lite, Pro, and Pro+ users of Wikidot.com automatically have API access. They need only to grab their key from their account settings before they can do anything. Free users can also access the API, but they must first request it here and wait for Wikidot to give it to them.

Note: Any free user that had an API key before this update took effect will still have access after the update. They need only to grab the new API key, as mentioned above, before anything will work.

More information/references:

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License