Unable to enable Aspose.Words Cloud or the Convert API

Aspose.Words Cloud Product Family
1

Hello Aspose Support,

My Aspose Cloud application is missing the “Products Used by This Application” section.

Because of this, I am unable to enable Aspose.Words Cloud or the Convert API.

My API calls return:
POST /v4.0/words/convert → 404 Not Found

Please enable the following APIs for my application:

:heavy_check_mark: Aspose.Words Cloud
:heavy_check_mark: Aspose.Words Cloud – Convert API
:heavy_check_mark: Aspose.Words Cloud – Advanced API
:heavy_check_mark: Aspose.PDF Cloud
:heavy_check_mark: Aspose.Storage Cloud (optional)

Application Name: Salesforce Test
Client ID: 037c0d0a-30b1-406a-b802-3e377092febc

Thank you!

2

@rishabhpal3112

Summary
You are receiving a 404 Not Found for the /v4.0/words/convert endpoint because the Aspose.Words Cloud (including the Convert and Advanced APIs) has not been provisioned for the Salesforce Test application. When a product is not attached to an application, its REST endpoints are not created, so any call to them returns 404 even with a valid access token.

Why it happens

  • The Products Used by This Application list for the app is empty, meaning none of the required Aspose Cloud products are enabled.
  • Without the product being enabled, the gateway does not expose the /words/convert endpoint, leading to the 404 response you see.

What to do next

  1. Check the product list – Log in to the Aspose Cloud portal, go to My Apps, select Salesforce Test, and verify that the Products Used by This Application section is empty.
  2. Request product enablement – In the same portal, use the Add Product (or Request Access) option to request the following products:
  • Aspose.Words Cloud
  • Aspose.Words Cloud – Convert API
  • Aspose.Words Cloud – Advanced API
  • (Optional) Aspose.PDF Cloud
  • (Optional) Aspose.Storage Cloud
    Submit the request. If you cannot add the products yourself, contact Aspose Support and provide your Client ID and Application Name; they can enable the products on your behalf.
  1. Wait for provisioning – After the request is processed, return to the app details and confirm that the selected products now appear in the Products Used list.
  2. Obtain a fresh OAuth 2.0 token – Use your Client ID and Client Secret to request a new access token (client‑credentials flow). A newly issued token reflects the current product permissions.
  3. Retest the endpoint – Call POST with the new token. If the products are correctly enabled, you should receive a successful response (e.g., 200 OK or 202 Accepted).
  4. If 404 persists – Verify that you are using the correct base URL for your account region (e.g., for US, for EU). Also ensure the token was generated after the products were attached.

If you continue to see a 404 after following these steps, please reply with the full request (including URL, headers, and body) and the exact response you receive so that the support team can investigate further.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.