PDQ expands API access & integrations across plans

PDQ has expanded API access and prebuilt integrations across all plan tiers, giving customers broader access to connections between PDQ and other IT systems.

It also added new API endpoints for custom fields, vulnerability data, and deployment status. The additions are intended to give IT teams more direct access to data used in device management, software deployment, and remediation.

The move reflects how many IT departments now operate across several platforms at once, including asset management tools, ticketing systems, security products, and internal automation tools. In that environment, administrators often have to export data manually, check deployment results in separate systems, and update records one step at a time.

Making API access available on every plan broadens access for customers that may previously have been limited to built-in workflows. Individual endpoints will still vary based on the features included in each plan.

New endpoints

The new endpoints cover three areas. Custom field management lets teams move device metadata into PDQ and allows external systems to update or retrieve those values. That could include ownership details, business unit information, or user data drawn from a configuration management database, directory service, asset platform, or internal tool.

A second set of endpoints lets customers retrieve vulnerability data from PDQ for reporting, compliance, ticketing, and security workflows. A third enables deployment status retrieval so outside systems can monitor whether software rollouts succeeded or failed and trigger follow-up actions when needed.

These additions are meant to help IT teams connect vulnerability management, software deployment, asset data, and remediation processes more effectively. Customers can build their own workflows through the API or use existing integrations.

Broader integrations

PDQ offers prebuilt integrations with a range of commonly used IT products, including Entra ID, Jira, Freshservice, Freshdesk, HaloPSA, HaloITSM, ServiceNow, Zendesk, and Zapier.

Its Zapier integration is one option for customers that do not want to build a custom integration from scratch. The connector supports workflows involving custom fields, vulnerability data, and deployment information across PDQ and other applications.

The update comes as software vendors serving IT operations face pressure to fit more easily into mixed technology environments rather than expecting customers to work within a single platform. Endpoint management products in particular are increasingly judged on how well they share data with service desks, security systems, and asset records.

PDQ, founded in 2001 and based in Salt Lake City, serves more than 33,000 customers. Its tools are used by system administrators, managed service providers, and IT teams managing Windows and macOS devices.

The company focuses on endpoint management, including patching, software deployment, and vulnerability management. The latest API changes suggest a stronger emphasis on making that operational data available beyond PDQ itself.

Mark Littlefield, Vice President of Product at PDQ, outlined the rationale for the changes.

"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."