Sankaku Channel/API post.xml (or .json) - Access Forbidden.

Most Danbooru-based sites I have gone to seem to be straightforward with the API use, but no matter what I do, I can't seem to figure out Sankaku's.

Going to:

http://chan.sankakucomplex.com/post/index.xml

Will give an error in Chrome (inspecting the page, this is just the XML header, but it has no content at all - not even an error message).

And then going to:

http://chan.sankakucomplex.com/post/index.json

Simply gives this JSON response:

{"success":false,"reason":"access denied"}

Naturally, I think authenticating would do the trick, but I can't do anything without knowing the password salt. The Sankaku API Help page states that:

password_hash: Your SHA1 hashed password. Simply hashing your plain password will NOT work since Danbooru salts its passwords.

Without the salt I cannot use the Danbooru API. Help, please?

Access to much of the API is currently restricted to higher level users and has been for some time.

We haven't had a chance to fully update the API to be compliant with our bilingual tagging system, and the API was in any case a source of significant abuse and would need further access control with the levels of traffic we see now, hence it not being fully accessible.

It'll be reinstated once full compliant again, most likely as a premium feature.

Apologies for the inconvenience! You can still contact us directly if there is anything in particular you need with respect to all this.

Incidentally, the password_hash is stored as a cookie on your local machine.

Thanks for the reply, System. :)

I have found my password_hash now and will try a few things to see if they work. I'm working on a booru client of sorts as a personal project so I'm checking the most popular ones to see how they are similar and how they are different.

If with this I can pull out posts, that will be fine, since that's pretty much everything I need to so. I can understand why there would be complications with the bilingual system.

EDIT: Turns out the response is a 403 one, so authenticating will make no difference unlike a 401 response.

Thanks again for your help System, I guess I will have to leave Sankaku Complex Chan out for now.

You may have trouble doing that as those are the main areas we had to restrict and rectify with respect to all the changes the bilingual tags introduced.

In any case it will eventually be available in full again with support for custom clients, and hopefully an official one of our own.

Yeah I just noticed the response is a 403 one, so authenticating will make no difference unlike a 401 response.

Thanks again for your help System, I guess I will have to leave Sankaku Complex Chan out for now. Keep up the good work and hopefully it will be usable for developers in the near future! :)

Let us know if you manage anything interesting, we're certainly hoping to support a variety of ways to access the site as a service in future.