Aspose.PDF retirement and latest API version

Aspose.PDF Cloud Product Family
1

Hi,

I’m reaching out to clarify the Aspose.PDF Cloud version retirement notice.

We’ve recently migrated from v1.1 to v3.0, but in your email, it states that Aspose.PDF Cloud (v3.0) will be retired on 15 November 2025.

From all the resources and documentation available online, v3.0 still appears to be the latest version of Aspose.PDF Cloud. Could you please confirm whether there is a newer version available?

I’ve attached a below the email for reference.

Dear Customer,

As part of our ongoing efforts to improve the performance, security, and maintainability of our platform, we are planning the following changes:

· Support for API Versions 1.0, 1.1, and 2.0 of all Aspose Cloud products will be fully retired.

· The following v3.0 modules , which were used in legacy integrations, will also be discontinued:

o Aspose.Words Cloud (v3.0)

o Aspose.PDF Cloud (v3.0)

o Aspose.HTML Cloud (v3.0)

o Aspose.Storage Cloud (v3.0)

· Additionally, the token generation endpoint /oauth2/token (used in cURL requests and direct API calls) will be retired. All integrations must switch to the newer /connect/token endpoint.

These versions will remain accessible until 15 November, after which all related services will be PERMANENTLY DECOMMISSIONED.

Our analysis indicates that you have used in the last 30 days at least one of the soon-to-be-retired versions. To avoid service disruption, please ensure you complete the migration to the latest supported version. You can find the most recent releases at:
https://releases.aspose.cloud/

Retiring legacy components allows us to focus on delivering a faster, more secure, and future-ready experience for all customers.

If you have questions or need support, please contact us at https://forum.aspose.cloud/.
We are fully committed to supporting you throughout this transition. Our team is available to assist with migration planning and provide usage summaries upon request.

Thank you for your continued partnership.

Best regards,

aspose.cloud sales

3

Hi,

Thank you for your response.

Would you be able to provide a link to the v4.0 API resources or documentation?

I’ve tried updating the URL to use v4.0, but I’m receiving a “404 Not Found” error, while the v3.0 endpoint continues to work correctly.

Tested URLs:

These were tested in Postman prior to migration.

We’ve also switched to using /connect/token for authentication, which works correctly with the v3.0 API.

Additionally, I reviewed the latest .NET SDK (aspose-pdf-cloud-dotnet) and noticed it still references v3.0 in its configuration file:
Configuration.cs – Line 55

string basePath = "https://api.aspose.cloud/v3.0";

We currently use the API directly (not the SDK), so confirmation on the correct v4.0 endpoint would be greatly appreciated.

4

Hi,

Additionally, the API Reference at Aspose.Pdf Cloud - API References is still showing v3.0 endpoints, with no mention of v4.0.

Any assistance you can provide would be greatly appreciated, as we’re getting closer to the retirement date and this is a critical component of our applications. This would cause a major disruption to our operations if unresolved.

If we’re unable to find a resolution soon, we’ll need to consider implementing a contingency plan to replace Aspose within our systems.

We’d be extremely grateful for your help in resolving this as soon as possible — any guidance, documentation, or clarification you can share would go a long way in helping us avoid disruption.

5

Hi,

Any update on this would be greatly appreciated.

As of Nov 07, 2025 — only 8 days before the scheduled outage — the Aspose.PDF v4.0 API still does not exist.

curl -X GET "https://api.aspose.cloud/v4.0/pdf" -H "accept: application/json"
# → 
# <html>
# <head><title>404 Not Found</title></head>
# <body>
# <center><h1>404 Not Found</h1></center>
# <hr><center>nginx</center>
# </body>
# </html>

But Aspose.Words v4.0 works:

curl -X GET "https://api.aspose.cloud/v4.0/words"
# → {
#  "Status": "Product is working fine!"
# }

Could you please provide an urgent update or timeline on when the v4.0 endpoints will be available?

Thank you for your prompt attention to this matter — any help at this stage would be sincerely appreciated.

6

Hi, @BigJohnny32_WHOOP
There is no version update for the Aspose Pdf Cloud API yet. Stay tuned for Word SDK updates on the Words forum.

7

Hi @kirill.novinskiy,

Thank you for the update, it’s greatly appreciated.

Just to clarify, will Aspose.PDF Cloud v3.0 still be available after 15 November 2025?

8

@BigJohnny32_WHOOP
Yes, it will be available: https://api.aspose.cloud/v3.0/pdf/

9

Is there a new deprecation date Aspose.PDF Cloud v3.0?

If not, where is the best place to track or be alerted to breaking changes?

10

Hi, @thomp361
No, there is no new deprecation date Aspose.PDF Cloud v3.0. You can see this on the release notes page: Aspose.PDF Cloud 25.10 Release Notes

11

@kirill.novinskiy

Thanks for the reply. I looked through all of the release notes and don’t see any mention of deprecation or the rescinding of this deprecation notice.

We’re about to go into production with several of your v3.0 endpoints, however, I am concerned as I am sure @BigJohnny32_WHOOP is, about the future and not being notified of breaking changes.

Is there an email list or a forum thread we could subscribe to so we can get emailed when changes are on the way?

12

@thomp361, We recommend using client SDK packages, so if you’re using a client SDK, the update process will proceed without changing the URL, as it’s hardcoded into the client SDK.
Current API references can be found at https://reference.aspose.cloud/.
There are currently no plans to upgrade to version 4, and there’s no specific notification mechanism other than the current emails.

13

@kirill.novinskiy

Got it. You mentioned the “current emails”, where/how can I make sure I am on that email list?

Whether using an SDK package or the endpoints directly, I’d like to be kept in the loop to make sure our production env doesn’t experience outages due to deprecation dates we weren’t aware of.

Thanks for your help

14

@thomp361, By “current emails,” I mean the email you use to log in to Containerize.IdentityServer - Single sign-on to access all applications and services of Aspose Pty Ltd. and receive notifications on it.

  1. You can subscribe to forum updates and receive email notifications to stay up-to-date on the latest news.
  2. You will also receive emails directly from the cloud platform, such as event notifications.
  3. Additionally, a new version of the cloud platform is released monthly, and you can follow updates on the release notes page.
  4. Client SDKs for various programming languages ​​are also published on GitHub, and you can set up notifications about new client SDK versions directly on GitHub.

Each notification method can be used to receive information about breaking changes in the relevant product.

15

Hey everyone, trying to understand this better.

Is the entire Aspose.pdf API going away? Or is Aspose delayed on the v3.0 update.

I notice that all the documentation today still points to v3 endpoints and the PythonSDK on GitHub is still using V3.

Some clarity would be great as the release notes seem to be pretty useless

16

Hi, @lucasmroberts
We recommend using client SDK packages, so if you’re using a client SDK, the update process will proceed without changing the URL, as it’s hardcoded into the client SDK. All client SDKs are updated regularly.
Current API references can be found at https://reference.aspose.cloud/ .

17

@lucasmroberts @kirill.novinskiy

The issue I’ve experienced with the cloud SDKs is that they often don’t match the API endpoints in terms of features. Documentation can be out of date as well. Also, some of the .NET versions have incorrectly implemented async context.

For production use cases and to keep your sanity, I highly recommend programming directly with the API endpoints themselves. I also wish we had better clarity on the PDF v3.0 deprecation timeline.

Don’t get me wrong, I love the aspose cloud services as I think the working product is the best on the market by a wide margin, but implementation and maintenance is a challenge.

18

@thomp361
Please refer to the documentation in the corresponding GitHub repository for the NET SDK: GitHub - aspose-pdf-cloud/Aspose.PDF-Cloud-SDK-for-.NET: .NET library for communicating with the Aspose.PDF Cloud API · GitHub