Pdq expands api access & integrations across plans

PDQ has expanded API access and prebuilt integrations across all of its plan tiers, opening access to more customers using its IT management tools.

It also introduced new API endpoints for custom fields, vulnerability data and deployment status. The additions are intended to help IT teams connect endpoint data with other systems they already use for asset management, ticketing, reporting and remediation.

Many IT teams rely on several tools to manage devices, monitor risk, verify software deployment outcomes and track follow-up actions. As a result, administrators often have to export data, check results manually and update records across separate systems.

PDQ's updated access model is designed to reduce that work by making API access available across all plans, although individual endpoints will still vary based on the features included in each tier.

Broader access

Customers can now choose between building their own workflows through the API or using prebuilt integrations. Supported integrations include Entra ID, Jira, Freshservice, Freshdesk, HaloPSA, HaloITSM, ServiceNow, Zendesk and Zapier.

The new API endpoints focus on three areas. One lets teams manage custom fields, including moving device metadata into PDQ and allowing external systems to update or retrieve those values. Another provides access to vulnerability data for reporting, compliance, security and ticketing workflows. A third delivers deployment results and status information so external systems can monitor outcomes and trigger follow-up actions.

These additions address a common operational problem for IT departments: business context, endpoint management and remediation tasks often sit in separate products. By expanding access to integrations and APIs, PDQ is aiming to make it easier for customers to connect those processes without building every step from scratch.

PDQ's Zapier integration can also support workflows involving custom fields, vulnerability data and deployment information, allowing customers to connect the platform with a wider range of software through Zapier's app library.

Operational focus

Founded in 2001 and based in Salt Lake City, PDQ serves more than 33,000 customers. Its software is used by system administrators, managed service providers and other IT teams to manage Windows and macOS devices, including patching, software deployment and vulnerability management.

Opening API access across all paid tiers may help PDQ expand the number of customers able to integrate its tools into internal systems, rather than limiting that option to higher-spending users. At the same time, it has maintained some differentiation between plans by making certain endpoints dependent on the functions available in each package.

Mark Littlefield, Vice President of Product at PDQ, said the change reflects the way IT operations are increasingly spread across multiple systems.

"IT teams rely on a growing set of systems to manage work, track issues, and prove progress," said Mark Littlefield, Vice President of Product at PDQ. "Our goal is to make PDQ easier to connect to those workflows so teams can automate more of the routine work and spend less time moving information between tools."