organization · inferred from evidence
Adobe
The maintainer of the PDF Services SDK and the team that closed the issue thread.
- Node SDK auth broke - migrate from service account to OAuth server-to-server creds
If your pdfservices-node-sdk calls die after the service-account deprecation, migrate to OAuth server-to-server credentials - build them with the service principal credentials builder using just your client ID and client secret, replacing t
- No public API for Adobe Extract usage data - only the console dashboard
There is no public API for Adobe PDF Services usage data, confirmed by a team member - the usage reports live only in the web console UI.
- pip dependency conflict: pdfservices SDK pins urllib3 - use a venv or GitHub master
Isolate the SDK in its own venv so its pinned urllib3 does not fight your other packages - a clean venv pulls 1.26.3 without conflict.
- Adobe PDF Services: use @adobe/pdfservices-node-sdk with ServicePrincipalCredentials
Use @adobe/pdfservices-node-sdk, not the old documentservices-pdftools package name.
- Fix ServiceApiError on Export PDF to Images by upgrading the SDK to 3.3.0
Teaches how to fix ServiceApiError on Export PDF to Images by upgrading the SDK to 3.3.0. Based on a real issue report and its verified fix.