Skip to main content

PDK API integration and cutover planning

PDK-specific planning is easiest when teams align early on partner requirements, API boundaries, and how account ownership affects future support and migration…

Written by Harman Sandhu
Updated this week

PDK API integration and cutover planning

PDK-specific planning is easiest when teams align early on partner requirements, API boundaries, and how account ownership affects future support and migration flexibility.

What this article covers

  • What matters about PDK partner access

  • Which API capabilities are relevant to Storify-style workflows

  • How account ownership and reprovisioning risks affect the plan

PDK integration shape

  • PDK API Integration: Step 1: Dealer Partnership Apply at prodatakey.com/request-partnership Purchase a PDK Demo Kit Complete technical certification at accesscontrol101.com Gives: Dealer Account, Customer Account creation, Cloud Node registration Step 2: API Partnership Visit prodatakey.com/become-a-partner/api or email integrations@prodatakey.com PDK reviews the request and discusses the project If approved: receive client_id and client_secret for OAuth2 API access This is approval-gated, not self-service. Not like Stripe where you sign up and get keys.

  • API Capabilities: Capability Details ------------ --------- REST API Full CRUD for organizations, systems, cloud nodes, people, credentials, doors Streaming API Real-time event stream Webhooks Push notifications for access events Mobile SDK iOS/Android for mobile credentials OAuth2 Standard third-party authentication Key quote from PDK: "Since these APIs power our own products, anything that can be done through pdk.io can also be incorporated into your application." Source: developer.pdk.io, support.pdk.io/hc/en-us/articles/14616036481431

  • What Storify Builds: The PDK adapter fits into the existing GateAdapter interface: ---

Hardware reprovisioning context

  • PDK Hardware Re-Provisioning: Technical Analysis: Short answer: Yes, but the current dealer (Storable) must release the Cloud Node first — or PDK support must intervene. --- PDK uses a hierarchical cloud topology: The Cloud Node serial number is the registration key.

Next steps

  • Use this when the project depends on PDK account transfer, dealer coordination, or hardware reuse assumptions.

References

Did this answer your question?