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
@BigJohnny32_WHOOP
Short answer
Yes – the notice is correct. Aspose.PDF Cloud v3.0 will be retired on 15 November 2025. The supported version after that date is v4.0. All new features, bug‑fixes and security updates are delivered only to v4.0, so you need to migrate before the retirement date.
What you have to change
| # |
Action |
How |
Why |
| 1 |
Update the API version in every request URL |
Change https://api.aspose.cloud/v3.0/... to https://api.aspose.cloud/v4.0/.... |
Calls to the v3.0 endpoint stop working after 15 Nov 2025. |
| 2 |
Use the new token endpoint |
POST to https://api.aspose.cloud/connect/token (instead of /oauth2/token). |
The old token endpoint is also being retired. |
| 3 |
Upgrade the SDK (if you use one) |
* .NET : Aspose.Pdf-Cloud ≥ 23.12.0
* Java : aspose-pdf-cloud ≥ 23.12.0
* Python : asposepdfcloud ≥ 23.12.0
* Node.js : asposepdfcloud ≥ 23.12.0 |
New SDK versions target v4.0 and include the updated authentication flow. |
| 4 |
Review the v4.0 breaking‑change notes |
Check the migration guide for renamed properties, removed parameters, and new enum values. |
Some v3.0 features have been renamed or removed; the SDK will surface compile‑time warnings. |
| 5 |
Test the updated integration |
Run a simple request (e.g., GET /pdf/{name}/pages) against the v4.0 endpoint with a fresh token. |
Confirms that authentication, URL format, and payloads are correct before the retirement date. |
Quick C# example – obtain a token and call a v4.0 operation
using System;
using System.Collections.Generic;
using System.Net.Http;
using System.Text.Json;
using System.Threading.Tasks;
using Aspose.Pdf.Cloud.Sdk.Api;
using Aspose.Pdf.Cloud.Sdk.Client;
public class PdfDemo
{
private const string ClientId = "YOUR_CLIENT_ID";
private const string ClientSecret = "YOUR_CLIENT_SECRET";
public static async Task Main()
{
// 1️⃣ Get an access token (new endpoint)
using var http = new HttpClient();
var tokenRequest = new HttpRequestMessage(HttpMethod.Post,
"https://api.aspose.cloud/connect/token")
{
Content = new FormUrlEncodedContent(new[]
{
new KeyValuePair<string, string>("grant_type", "client_credentials"),
new KeyValuePair<string, string>("client_id", ClientId),
new KeyValuePair<string, string>("client_secret", ClientSecret)
})
};
var tokenResponse = await http.SendAsync(tokenRequest);
tokenResponse.EnsureSuccessStatusCode();
var tokenJson = await tokenResponse.Content.ReadAsStringAsync();
var accessToken = JsonDocument.Parse(tokenJson)
.RootElement.GetProperty("access_token")
.GetString();
// 2️⃣ Configure the SDK for v4.0
var config = new Configuration
{
BasePath = "https://api.aspose.cloud/v4.0",
AccessToken = accessToken
};
var pdfApi = new PdfApi(config);
// 3️⃣ Call a simple operation – get page count
var result = await pdfApi.GetDocumentPageCountAsync("sample.pdf");
Console.WriteLine($"Page count: {result.Value}");
}
}
Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with the values from your Aspose Cloud dashboard.
Where to find the official information
- Releases page – lists the latest v4.0 package and changelog.
- API reference (v4.0) – up‑to‑date operation definitions and request/response schemas.
- Migration guide – step‑by‑step instructions for moving from v3.0 to v4.0, including the new token endpoint.
All three are available from the Aspose Cloud portal.
Need help?
- Support forum – post “Aspose.PDF Cloud v4 migration” and tag
aspose-pdf-cloud.
- Customer support ticket – open a ticket from the Aspose Cloud console for personalized assistance.
Bottom line – migrate to Aspose.PDF Cloud v4.0 (and the /connect/token endpoint) as soon as possible to avoid any service interruption after 15 Nov 2025. The release page, API reference, and migration guide contain everything you need for a smooth transition.
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.
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.
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.
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.
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?
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?
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
@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?
@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.
@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
@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.
- You can subscribe to forum updates and receive email notifications to stay up-to-date on the latest news.
- You will also receive emails directly from the cloud platform, such as event notifications.
- Additionally, a new version of the cloud platform is released monthly, and you can follow updates on the release notes page.
- 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.
v3.0: 
v4.0: