Summary and recommendation
PDQ Deploy exposes no public REST API, no OAuth or token-based authentication system, and no user management endpoints.
It is a Windows-native desktop application;
all administrative actions are performed through the application UI.
No official developer documentation for a user-management API has been published by PDQ as of the research date.
PDQ Deploy does support PowerShell scripting for package deployment automation, but this is a deployment workflow mechanism
it is not a user management API and cannot be used to provision, deprovision, or modify admin access programmatically.
For teams requiring programmatic integration into an identity graph - mapping app access back to a canonical user identity across systems - PDQ Deploy presents a hard gap.
There is no API surface to query current access state, no webhook to signal access changes, and no SCIM endpoint to receive provisioning events from an IdP.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | N/A |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No webhook system is documented in official PDQ Deploy help or developer resources.
Alternative event strategy: PDQ Deploy supports PowerShell-based scripting and scheduled task triggers within the application itself as a workflow alternative.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No SCIM provisioning support documented by PDQ for PDQ Deploy.
- No IdP integrations (Okta, Entra ID, Google Workspace, OneLogin) are officially supported for automated user provisioning.
Common scenarios
No supported API scenarios exist for user lifecycle management in PDQ Deploy.
The following integration patterns are explicitly unsupported:
- SCIM provisioning from Okta, Entra ID, Google Workspace, or OneLogin: not documented, not available.
- REST API calls to list, create, or deactivate admin users: no endpoint exists.
- Webhook-driven deprovisioning on user offboarding events: no webhook system is documented.
- Token-based authentication for automated access audits: no auth mechanism is published.
The only programmatic surface available is PowerShell scripting scoped to package deployment tasks, not identity or access management.
If programmatic integration is a requirement, PDQ Connect should be evaluated separately against current PDQ documentation, as its API capabilities may differ.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The absence of any user management API in PDQ Deploy creates a structural blind spot for teams building automated identity workflows.
Because access is controlled at the Windows OS layer rather than through an application identity model, there is no reliable programmatic method to determine who currently has access to a given PDQ Deploy installation, whether that access is still appropriate, or when it was last used.
This makes PDQ Deploy opaque to identity graph construction: you cannot pull a current access roster via API, you cannot subscribe to access-change events, and you cannot push deprovisioning commands from a central IdP.
Any access audit requires manual inspection of Windows permissions on each host machine and a separate review of account.pdq.com for license assignments.
Teams that treat the identity graph as a source of truth for app access will need to treat PDQ Deploy as a manually maintained exception until PDQ publishes an API surface - or until the workload migrates to PDQ Connect.
Automate PDQ Deploy workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
