Thank you for checking the account.
We are integrating Aspose.CAD Cloud into a WordPress/PHP application. The calls are made server-side from PHP, not from the browser.
Our task is to convert uploaded CAD files, primarily DWG and DXF, into GLB/GLTF for 3D rendering inside our application.
For authentication we are using the OAuth client-credentials flow.
Token server:
https://id.aspose.cloud/connect/token
We have also tested the older/fallback endpoint:
https://api.aspose.cloud/connect/token
We successfully receive an OAuth access token from Aspose.
CAD API endpoint:
https://api.aspose.cloud/v3.0/cad
The problem occurs when we then call the Aspose.CAD API using the returned bearer token. The CAD request returns an Unauthorized / errorAuthorization response.
Our diagnostics indicate that the access token is being issued successfully, but it does not appear to include access to the CAD API / api.cad scope or entitlement.
The workflow we are trying to achieve is:
- User uploads a DWG or DXF file to our server.
- Our PHP server obtains an OAuth token using the Aspose Client ID and Client Secret.
- Our server submits the CAD file to Aspose.CAD Cloud.
- Aspose converts the file to GLB.
- We download the resulting GLB back to our server.
We are not attempting to call the API through JavaScript/CORS. CORS Origin is therefore left blank in the Aspose application settings.
The account dashboard shows the Free Plan as active and API calls are available.
Could you please confirm:
- whether
https://id.aspose.cloud/connect/token is the correct OAuth token endpoint for Aspose.CAD Cloud;
- whether
https://api.aspose.cloud/v3.0/cad is the correct base CAD API endpoint;
- whether our application should receive an
api.cad scope/permission in the OAuth token;
- and which exact Aspose.CAD REST endpoint/request you recommend for converting a DWG or DXF file to GLB?
If helpful, we can provide the exact HTTP request and sanitized response from our diagnostics, with the Client Secret and access token removed.