You can find the documentation for our download center API: here

I presume this is upcoming stuff that's different from the current update check you guys have set up?

3 hours ago, Stealth22 said:

I presume this is upcoming stuff that's different from the current update check you guys have set up?

We've added a beta value to check the latest beta version of the file. Also an API for validating beta users if you choose to use the beta system.

I've included an example C# implementation with both of the API documentations.

This is based on stuff we've used for LCPDFR, and a little bit for LSPDFR.

Is there anything in the works (jwt, oauth2) for authenticating users against lcpdfr?

Awesome addition, thank you!

Is there any more information available regarding the beta system? Do we need to setup authorized users, or can it be used to somehow highlight that a plugin is still in beta?

9 hours ago, Darkmyre said:

Awesome addition, thank you!

Is there any more information available regarding the beta system? Do we need to setup authorized users, or can it be used to somehow highlight that a plugin is still in beta?

Hoping to document this later. Basically on your files you can now upload a beta version, by choosing the 'Upload beta version' File Actions option. You can then manage users who can download this beta version inside the 'Manage testers'  File Actions option.

11 hours ago, ainesophaur said:

Is there anything in the works (jwt, oauth2) for authenticating users against lcpdfr?

This isn't planned right now, sorry.

<snip>

Edited June 19, 201610 yr by Albo1125

It looks like (among other things) our update checking API was abused to cause excess load. We're looking into a way to sort this out, but in the mean time the update checking API may be returning an error.

11 minutes ago, Cyan said:

It looks like (among other things) our update checking API was abused to cause excess load. We're looking into a way to sort this out, but in the mean time the update checking API may be returning an error.

I'm going to be changing my plugins to only call the API once every 24 hours, or something. 

2 minutes ago, Stealth22 said:

I'm going to be changing my plugins to only call the API once every 24 hours, or something. 

It wasn't legitimate traffic, so you don't need to worry. This was someone who deliberately flooded the API with requests; and I'm 100% sure it did not come from any API developers' plugin.

2 hours ago, Cyan said:

It wasn't legitimate traffic, so you don't need to worry. This was someone who deliberately flooded the API with requests; and I'm 100% sure it did not come from any API developers' plugin.

It's a pity that once a topic like this is created, it's instantly abused in such a way.

It's been available for months without issue only because you only mentioned it in a reply.

I'm investigating an issue with the API and I'm hoping to resolve it as soon as possible.

Update: Now available again.

https has been enabled for APIs above. More news soon.

Did the beta upload system get removed at somepoint, i know this post is 4 years old so just thought i would ask?

35 minutes ago, OfficerPope said:

Did the beta upload system get removed at somepoint, i know this post is 4 years old so just thought i would ask?

It was deprecated and later removed, unfortunately there wasn't enough uptake to justify maintaining it with ongoing website updates.

• Moved documentation to GitHub pages.
• Added a new call getAssemblies to grab assembly versions of a file given its ID.

That's awesome, thank you.

Just so you're aware you haven't yet updated the information when you embed the site.

Documentation for the Kittn API
 

1 hour ago, Cyan said:

• Moved documentation to GitHub pages.
• Added a new call getAssemblies to grab assembly versions of a file given its ID.

 

This doesn't seem to work for some files. Example: https://www.lcpdfr.com/applications/downloadsng/interface/api.php?fileId=41551&do=getAssemblies

We're seeing excessive use on some of these APIs.
 

Requests without a User Agent will soon be throttled by IP address to 20 req/minute. However, we will try to avoid throttling requests from LSPDFR plugins based on some data we have.

 

Requests with a valid User Agent (e.g. something like in the linked API page that shows what and how to contact the author of the plugin/service) will soon be throttled by IP address to 60 req/minute (1req/s). Requests that exceed this will receive 403 errors and excessive 403s will cause temporary blocks.

If you have a specific use case which requires calling these APIs more than once a second, please reach out with your use case and what efforts you've done to reduce calls (e.g. caching). We can make special exceptions for some user agents.