Overview

PDXpert WebAPI gives your team a practical integration layer for Parts, Documents, BOMs, Changes, RevisionFiles, and ItemFiles while keeping your deployment fully self-hosted. The API and data remain inside infrastructure you control, so only systems explicitly permitted by your IT and security policies can access product data.

• Integrate engineering data with ERP, analytics, and internal workflow tools.
• Keep governance and network access aligned to your internal IT controls.
• Deploy in environments that require controlled, self-hosted system boundaries.

We provide the API download package and installation assistance after an agreement is signed.

Product Example

Typical buyer use-cases include authenticated data retrieval, downstream system synchronization, and selective data exposure for reporting and automation.

System Requirements and Dependencies

Sizing / system requirements (guideline): Resource needs depend on transaction volume, concurrency, integrations, authentication usage, and growth. The guidance below is a starting point and should be validated against real usage and your organizational standards.

• Dedicated API server (separate from PDXpert server): Start by matching the standard PDXpert Server hardware configuration (CPU, RAM, storage) as a baseline.
• Co-located deployment (WebAPI on the same server as PDXpert): Start at approximately 1.5x the standard PDXpert Server resource profile to account for API workload.
• Expected load guideline: Baseline guidance assumes peak load around 50 active users, each making 1-2 API calls per second. Higher concurrency may require additional tuning or scaling.
• Post go-live recommendation: Monitor CPU, memory, disk I/O, and IIS request throughput under typical and peak load, then adjust resources accordingly.
• Platform prerequisites: Windows Server 2022/2025, IIS with ASP.NET/.NET Framework 4.8 hosting prerequisites, and a corresponding compatible version of PDXpert PLM.
• PDXpert API license.
• Self-hosted deployment with HTTPS and IT-controlled network access rules.

2.1 Authentication and session behavior

• One active session per user: each user has one active API session backed by a PDXpert server connection. Logging in again (for example, a new /token request with the same credentials) replaces the previous session.
• Effect of re-login: requests still using the old session may receive 401 Unauthorized or equivalent failures. Integrations should treat 401 as a signal to re-authenticate, obtain a new access token, and retry using the new token.

Licensing Terms

PDXpert WebAPI licensing is aligned to project scope and integration requirements. Contact us to review your use case, system architecture, and deployment model so we can recommend the right licensing approach.