2 hours ago, Cyan said:

Requests that exceed this will receive 403 errors and excessive 403s will cause temporary blocks.

 

You should use status code 429 for rate limit throttling, not 403.

 

Could you please investigate why the assembly version functionality doesn't work for some files? 

Edited December 16, 20232 yr by PNWParksFan

7 minutes ago, PNWParksFan said:

 

You should use status code 429 for rate limit throttling, not 403.

 

Could you please investigate why the assembly version functionality doesn't work for some files? 

We should use 429 however, for legacy reasons, this will not be possible at this time.

 

There is a note on the API page as to why this will not work for every file, basically a reprocessing has to happen for older files, this hasn't been done yet, but when it's done I'll update this thread.

The API documentation has been updated to cover a new function getAllVersions which allows checking for file updates in bulk.

.NET assembly versions should now be available for all files. 

As a reminder, the API documented in this article has been deprecated and is being retired in stages.

The “Get user-facing version for a file” request, do=checkForUpdates, has already stopped working for new files uploaded after 8 May 2026.

We currently intend to turn off all remaining endpoints on 1 June 2026 and are moving to our new authenticated API.

For checking updates to your own files, we recommend using our new Version Check Keys. These include API documentation in your Account Settings. Please note that Version Check Keys are limited to checking updates for files you own.

For other use cases, our new Public API keys are available on request for non-commercial use. These allow you to retrieve file details in bulk, up to 10,000 files at a time, sorted by file update date by default. These new endpoints include far more details about files, including tags, screenshots and more.

We plan to share more in the coming months about the full deprecation of the “Get user-facing version for a file” endpoint. If you have any questions, please let us know.

On 5/21/2026 at 6:27 AM, Cyan said:

As a reminder, the API documented in this article has been deprecated and is being retired in stages.

The “Get user-facing version for a file” request, do=checkForUpdates, has already stopped working for new files uploaded after 8 May 2026.

We currently intend to turn off all remaining endpoints on 1 June 2026 and are moving to our new authenticated API.

For checking updates to your own files, we recommend using our new Version Check Keys. These include API documentation in your Account Settings. Please note that Version Check Keys are limited to checking updates for files you own.

For other use cases, our new Public API keys are available on request for non-commercial use. These allow you to retrieve file details in bulk, up to 10,000 files at a time, sorted by file update date by default. These new endpoints include far more details about files, including tags, screenshots and more.

We plan to share more in the coming months about the full deprecation of the “Get user-facing version for a file” endpoint. If you have any questions, please let us know.

June 1st is very soon, and this is the first I'm hearing of this change. Could you please give us a bit more time to update existing mods that use the existing endpoints, and make a standalone announcement in the API Development subforum and on the developers Discord?

On 5/24/2026 at 3:51 AM, PNWParksFan said:

June 1st is very soon, and this is the first I'm hearing of this change. Could you please give us a bit more time to update existing mods that use the existing endpoints, and make a standalone announcement in the API Development subforum and on the developers Discord?

I 2nd this. More time would be a good thing.

Replied in the developer Discord:

The change on June 1st is just the extended APIs (do=getAssemblies,do=getAllVersions) the main users of this (discord bots) have already migrated to the new API. Infact, I'm not seeing any usage from our telemetry data (apart from a really badly misconfigured plugin that is receiving an error response anyway) in the past 24 hours.

The legacy check for updates API has been phased out for new files, but for existing files this will be done in staged brownouts later in the year (with better notice). We'll obviously need to assess if it's even viable to completely get rid of, whitelist certain things that break that aren't going to be fixed/etc (although ultimately our hand might be pushed on it at some point - if we have to turn off old TLS versions for a critical security issue for example). If you're using checkForUpdates there will be no change on June 1st.

Sorry, my initial post is a little unclear.