{"id":7986,"date":"2026-09-04T06:55:01","date_gmt":"2026-09-04T06:55:01","guid":{"rendered":"https:\/\/www.purevpn.com\/white-label\/?p=7986"},"modified":"2026-09-04T06:55:03","modified_gmt":"2026-09-04T06:55:03","slug":"dpp-api-integration","status":"publish","type":"post","link":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/","title":{"rendered":"DPP API Integration: Two Privacy Products, One Account"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_71 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-transparent ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#What_Staying_on_Two_Roadmaps_Costs_an_MSP\" title=\"What Staying on Two Roadmaps Costs an MSP\">What Staying on Two Roadmaps Costs an MSP<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Why_This_Cannot_Wait\" title=\"Why This Cannot Wait\">Why This Cannot Wait<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#What_DPP_API_Integration_Actually_Adds_to_an_Existing_VPN_Stack\" title=\"What DPP API Integration Actually Adds to an Existing VPN Stack\">What DPP API Integration Actually Adds to an Existing VPN Stack<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Identity_Exposure_Intelligence\" title=\"Identity Exposure Intelligence\">Identity Exposure Intelligence<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Real_Time_Monitoring_Versus_Manual_Rechecking\" title=\"Real Time Monitoring Versus Manual Rechecking\">Real Time Monitoring Versus Manual Rechecking<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Data_Broker_Opt-Out_Lifecycle\" title=\"Data Broker Opt-Out Lifecycle\">Data Broker Opt-Out Lifecycle<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#How_the_Account_Layer_Works_Across_Both_APIs\" title=\"How the Account Layer Works Across Both APIs\">How the Account Layer Works Across Both APIs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#The_Provisioning_Sequence_Question\" title=\"The Provisioning Sequence Question\">The Provisioning Sequence Question<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Billing_and_Margin_Impact_for_MSPs\" title=\"Billing and Margin Impact for MSPs\">Billing and Margin Impact for MSPs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#What_a_Technical_Evaluation_Actually_Needs_to_Confirm\" title=\"What a Technical Evaluation Actually Needs to Confirm\">What a Technical Evaluation Actually Needs to Confirm<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#What_Happens_When_a_Call_Fails\" title=\"What Happens When a Call Fails\">What Happens When a Call Fails<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Access_Token_Expiry\" title=\"Access Token Expiry\">Access Token Expiry<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Opt-Out_Failures_Versus_Monitoring_Failures\" title=\"Opt-Out Failures Versus Monitoring Failures\">Opt-Out Failures Versus Monitoring Failures<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Compliance_and_Data_Handling_Across_Both_Layers\" title=\"Compliance and Data Handling Across Both Layers\">Compliance and Data Handling Across Both Layers<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Where_This_Fits_for_MSPs_Already_Running_VPN_Infrastructure\" title=\"Where This Fits for MSPs Already Running VPN Infrastructure\">Where This Fits for MSPs Already Running VPN Infrastructure<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#Final_Thoughts\" title=\"Final Thoughts\">Final Thoughts<\/a><\/li><\/ul><\/nav><\/div>\n\n<link href=\"https:\/\/fonts.googleapis.com\/css2?family=Poppins:wght@500;600&#038;display=swap\" rel=\"stylesheet\">\n\n<style>\n  .tldr-box {\n    font-family: 'Poppins', sans-serif;\n    max-width: 800px;\n    margin: 40px auto;\n    background: #F9F7FF;\n    border: 1px solid #D9D2F5;\n    border-radius: 12px;\n    box-shadow: 0 8px 25px rgba(166, 143, 239, 0.08);\n    padding: 25px 30px;\n    display: flex;\n    flex-direction: column;\n    align-items: center;\n  }\n\n  .tldr-title {\n    font-weight: 700;\n    font-size: 28px;\n    color: #4D3B7A;\n    margin-bottom: 20px;\n    text-align: center;\n  }\n\n  .tldr-content ul {\n    margin: 0;\n    padding-left: 20px;\n    color: #4D3B7A;\n    font-size: 15px;\n    line-height: 1.7;\n    width: 100%;\n  }\n\n  .tldr-content li {\n    margin-bottom: 8px;\n  }\n\n  .tldr-content strong {\n    font-weight: 600;\n    color: #4D3B7A;\n  }\n<\/style>\n\n<div class=\"tldr-box\">\n  <div class=\"tldr-title\">Key Takeaways<\/div>\n  <div class=\"tldr-content\">\n    <ul>\n      <li><strong>DPP API integration shares the VPN account&#8217;s authentication layer:<\/strong> both surfaces exchange the same Secret Key for a bearer access token under one partner account, so no second auth model or security review is needed.<\/li>\n      <li><strong>The two products track different lifecycles:<\/strong> VPN accounts move through create, enable, and renew states, while data privacy protection follows a five stage opt-out lifecycle from submitted to re-listed.<\/li>\n      <li><strong>Provisioning stays independent:<\/strong> a VPN account and an identity exposure record are created separately, since no single endpoint combines both objects.<\/li>\n      <li><strong>It moves the economics for MSPs:<\/strong> bundled privacy and VPN products see roughly 78 percent renewal and 50 percent lower churn compared to single-product accounts, and billing runs on the same per-seat model already used for VPN.<\/li>\n      <li><strong>Integration timeline is short for teams with an existing VPN build:<\/strong> most partners add identity exposure and monitoring endpoints in one to two sprints, since the authentication work is already done.<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\n\n\n<p>MSPs already <a href=\"https:\/\/www.purevpn.com\/vpn-reseller\/free-white-label-reseller-business-opportunities\/\" target=\"_blank\" rel=\"noreferrer noopener\">reselling a white label VPN<\/a> often lose expansion revenue. A client asks for breach monitoring or <a href=\"https:\/\/www.purevpn.com\/white-label\/white-label-data-roker-removal\/\" target=\"_blank\" rel=\"noreferrer noopener\">data removal,<\/a> and the MSP has nothing to offer. Adding it usually means a second vendor, a second billing relationship, and a separate provisioning flow for every client account. DPP API integration removes that requirement when the MSP already runs the underlying VPN account API.<\/p>\n\n\n\n<p>One infrastructure provider runs both product lines under a single partner account. VPN account management and data privacy protection sit on separate endpoint groups. But the two surfaces connect underneath. Understanding how they connect changes how an MSP scopes the work and prices the add-on.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Staying_on_Two_Roadmaps_Costs_an_MSP\"><\/span><strong>What Staying on Two Roadmaps Costs an MSP<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"740\" height=\"420\" src=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20110820\/Internal-Images-2026-07-20T155525.627.png\" alt=\"Infographic titled 'Costs of Two Roadmaps' comparing duplicate operating costs against the benefits of unified integration across auth reviews, support, and revenue.\" class=\"wp-image-7988\" srcset=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20110820\/Internal-Images-2026-07-20T155525.627.png 740w, https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20110820\/Internal-Images-2026-07-20T155525.627-705x400.png 705w\" sizes=\"(max-width: 740px) 100vw, 740px\" \/><\/figure>\n\n\n\n<p>For MSPs, every separately managed privacy integration adds another provisioning workflow and another support queue. A second vendor means a second security review before anything ships to clients. It also means a second contract, a second SLA to track, and a second escalation path when something breaks.<\/p>\n\n\n\n<p>That cost shows up in three places:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Duplicate authentication review:<\/strong> security teams evaluate a new vendor&#8217;s auth model from scratch, instead of reusing an approval already on file.<\/li>\n\n\n\n<li><strong>Duplicate support ownership:<\/strong> two vendors means two places a ticket can stall while each side points at the other.<\/li>\n\n\n\n<li><strong>Delayed cross-sell revenue:<\/strong> the longer the add-on stays unshipped, the longer it stays out of the upsell conversation.<\/li>\n<\/ul>\n\n\n\n<p>Integrating <a href=\"https:\/\/www.purevpn.com\/white-label\/digital-privacy-protection-for-saas\/\" target=\"_blank\" rel=\"noreferrer noopener\">DPP into an existing VPN <\/a>account avoids that duplicate operating cost. The authentication work and the partner relationship already exist.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Why_This_Cannot_Wait\"><\/span><strong>Why This Cannot Wait<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>A 2025 survey on <a href=\"https:\/\/www.ibm.com\/think\/topics\/api-sprawl\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">API security<\/a> found that 57 percent of organizations suffered an API-related breach in two years. The same survey found organizations run 10 to 20 percent more active APIs than their security teams track. Every new integration a partner builds separately adds to that exposure.<\/p>\n\n\n\n<p>The revenue case moves just as fast. MSPs that already cross-sell privacy services alongside their core offering see a 78 percent renewal rate, well above single-product accounts. Bundled users also churn roughly 50 percent less than clients on one product alone. Waiting on a second integration project means missing that renewal pattern while competitors already package privacy at checkout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_DPP_API_Integration_Actually_Adds_to_an_Existing_VPN_Stack\"><\/span><strong>What DPP API Integration Actually Adds to an Existing VPN Stack<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"740\" height=\"420\" src=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20112101\/Internal-Images-2026-07-20T160234.514.png\" alt=\"Simple and minimal graphic that maps out the three key functions added by the DPP API to an existing VPN stack.\" class=\"wp-image-7989\" srcset=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20112101\/Internal-Images-2026-07-20T160234.514.png 740w, https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20112101\/Internal-Images-2026-07-20T160234.514-705x400.png 705w\" sizes=\"(max-width: 740px) 100vw, 740px\" \/><\/figure>\n\n\n\n<p>A data privacy protection layer covers three distinct functions. Each one maps to its own endpoint group, not one general purpose call.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Identity_Exposure_Intelligence\"><\/span><strong>Identity Exposure Intelligence<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>The identity exposure endpoint accepts an email, phone number, or username. It returns a consolidated report of where that identifier surfaced in known breaches. A partner submits one identifier per call and gets breach sources back, not a simple yes or no flag. That detail matters for remediation. A password from an old breach needs different guidance than a card number from a recent leak.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Real_Time_Monitoring_Versus_Manual_Rechecking\"><\/span><strong>Real Time Monitoring Versus Manual Rechecking<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Once exposure is confirmed, a partner can register the same asset for continuous <a href=\"https:\/\/www.purevpn.com\/white-label\/how-dark-web-monitoring-works\/\" target=\"_blank\" rel=\"noreferrer noopener\">dark web monitoring<\/a>. That replaces re-scanning it by hand. The monitoring service watches marketplaces, forums, and paste sites. It pushes a webhook the moment the asset reappears. A partner that skips this step ends up polling on a fixed schedule instead. That delays detection and adds unnecessary call volume against rate limits.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Data_Broker_Opt-Out_Lifecycle\"><\/span><strong>Data Broker Opt-Out Lifecycle<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>A partner submits a user&#8217;s name and email to start an opt-out request. From there, it moves through five defined states:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Submitted:<\/strong> the request is created and queued for processing.<\/li>\n\n\n\n<li><strong>In progress:<\/strong> the service is actively contacting the broker.<\/li>\n\n\n\n<li><strong>Pending verification:<\/strong> the broker requires confirmation before removal.<\/li>\n\n\n\n<li><strong>Completed:<\/strong> the broker confirms the data is gone.<\/li>\n\n\n\n<li><strong>Re-listed:<\/strong> the data reappears, and a new request files automatically.<\/li>\n<\/ul>\n\n\n\n<p>A single user can carry multiple opt-out requests in flight at once. Brokers do not process removals on the same schedule. More than 400 brokers fall under this coverage today. A partner is not filing one request per user, but potentially dozens across the broker landscape. DPP API integration handles that volume through status polling on the opt-out endpoint, not a webhook. Broker responses do not arrive the way breach alerts do.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_the_Account_Layer_Works_Across_Both_APIs\"><\/span><strong>How the Account Layer Works Across Both APIs<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>VPN account management and data privacy protection sit on different endpoint groups. But they share the same partner account structure underneath.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Layer<\/strong><\/td><td><strong>Primary Object<\/strong><\/td><td><strong>Auth Pattern<\/strong><\/td><td><strong>Lifecycle Model<\/strong><\/td><td><strong>Delivery Method<\/strong><\/td><\/tr><tr><td>VPN Account Management<\/td><td>VPN account, tied to subscription type<\/td><td>Secret Key to bearer access token<\/td><td>Create, generate, extend, renew, enable, disable, delete<\/td><td>Request and response, status polling<\/td><\/tr><tr><td>Data Privacy Protection<\/td><td>Identity record, tied to email or phone<\/td><td>Secret Key to access token via auth endpoint<\/td><td>Submitted, in progress, pending verification, completed, re-listed<\/td><td>Webhook for monitoring, polling for opt-out<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Both API surfaces authenticate the same way. A Secret Key exchanges for a bearer access token, tied to a single partner or reseller ID. A partner that already integrated VPN account management does not need a new authentication model to add DPP API integration. It needs a second set of endpoints, evaluated on their own merits rather than a second security review.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Provisioning_Sequence_Question\"><\/span><strong>The Provisioning Sequence Question<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Partners often ask whether DPP API integration needs to run before or after VPN account creation. The two are independent. A VPN account grants network access, tied to a subscription type, a country inventory, and a protocol list. An identity record tracks exposure instead, tied to an email or phone number, not a subscription.<\/p>\n\n\n\n<p>A partner can provision a VPN account first. Identity monitoring can get added weeks later without breaking either object. Sequencing only matters for one case: onboarding flow design. Consider an MSP adding a privacy add-on to an existing client&#8217;s VPN plan. The VPN account already exists at signup. Adding identity exposure intelligence at that point means one additional call. It uses the client&#8217;s email as the identifier, fired right after account confirmation returns. The two calls do not depend on each other. A failure in one does not roll back the other.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Billing_and_Margin_Impact_for_MSPs\"><\/span><strong>Billing and Margin Impact for MSPs<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>DPP API integration bills per user rather than per feature, the same model VPN accounts already use. An MSP adding privacy monitoring to an existing base of client seats can model margin before committing to it. The same per-seat math already applies to VPN pricing.<\/p>\n\n\n\n<p>That consistency matters for how the add-on gets sold. A separate vendor usually means a separate pricing model. That forces a new margin calculation and a new line item on every client invoice. Running both products through one partner account keeps the pricing structure the client already understands. The MSP&#8217;s own margin math stays in one place, not two.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_a_Technical_Evaluation_Actually_Needs_to_Confirm\"><\/span><strong>What a Technical Evaluation Actually Needs to Confirm<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>A handful of details decide most technical evaluations, and generic VPN content rarely covers them. A second Secret Key is not part of the picture. Both surfaces authenticate against the same partner account. Each session simply issues its own access token from that one key.<\/p>\n\n\n\n<p>Rate limits stay separate as well. Each API surface tracks its own call volume. A spike in opt-out status checks does not throttle VPN account calls on the other surface. Reporting works the same way, since usage dashboards break volume out by product line rather than showing one blended number.<\/p>\n\n\n\n<p>A partner with an existing VPN integration typically adds identity exposure and monitoring endpoints in one to two sprints. The auth layer already exists and does not need rebuilding. Most of that time goes into mapping opt-out lifecycle states into the partner&#8217;s own support tooling. Authentication work takes little of it.<\/p>\n\n\n\n<p>Incident ownership splits cleanly between the two parties. The infrastructure partner owns detection and opt-out mechanics. The MSP owns client communication and in-product alerting. A partner that skips defining this split up front usually builds duplicate alerting logic. Both sides end up assuming the other handles client notification.<\/p>\n\n\n\n<p>Compliance scope does shift once both products run together. Identity data processing adds a sub-processor relationship. That relationship needs to appear in the partner&#8217;s own data processing agreement. It sits alongside any VPN sub-processor language already on file.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Happens_When_a_Call_Fails\"><\/span><strong>What Happens When a Call Fails<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"740\" height=\"420\" src=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20112239\/Internal-Images-2026-07-20T155934.531.png\" alt=\"Infographic titled 'API Call Failures' illustrating workflows for token expiry, opt-out auto-retries, and immediate monitoring failures.\" class=\"wp-image-7991\" srcset=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20112239\/Internal-Images-2026-07-20T155934.531.png 740w, https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20112239\/Internal-Images-2026-07-20T155934.531-705x400.png 705w\" sizes=\"(max-width: 740px) 100vw, 740px\" \/><\/figure>\n\n\n\n<p>Generic API guides cover error codes in the abstract. A <a href=\"https:\/\/www.purevpn.com\/white-label\/purevpn-apis-documentation-explained-for-developers\/\" target=\"_blank\" rel=\"noreferrer noopener\">partner building DPP API integration<\/a> alongside a VPN account needs to know what happens when a call fails. The failure modes do not always overlap.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Access_Token_Expiry\"><\/span><strong>Access Token Expiry<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Both API surfaces issue access tokens with a defined expiry, returned in seconds at the time of the token exchange. A call made after expiry fails authentication on that surface only. The fix is a refresh token call, not a full re-authentication. A partner running both products needs two refresh cycles tracked in parallel. Each surface issues its own token, even though both trace back to one Secret Key.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Opt-Out_Failures_Versus_Monitoring_Failures\"><\/span><strong>Opt-Out Failures Versus Monitoring Failures<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>A failed opt-out submission and a failed monitoring registration behave differently. An opt-out request that fails at the broker level moves to a retry queue automatically. Brokers reject malformed submissions for reasons outside the partner&#8217;s control. A monitoring registration failure is usually immediate and tied to a malformed identifier. It surfaces back to the partner at call time, not during a background retry.<\/p>\n\n\n\n<p>This distinction matters for how a partner builds its own retry logic. Treating both failure types the same way causes problems. It either floods the opt-out endpoint with retries, or drops a monitoring registration that needed an immediate fix.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Compliance_and_Data_Handling_Across_Both_Layers\"><\/span><strong>Compliance and Data Handling Across Both Layers<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Running VPN and data privacy protection under one integration does not merge their compliance obligations. It adds them together instead. VPN traffic falls under standard no-log commitments. Identity exposure checks and broker opt-out requests involve personally identifiable information, which carries separate handling requirements.<\/p>\n\n\n\n<p>The underlying infrastructure is SOC 2 Type II certified. Its no-log policy is verified through a KPMG audit. That certification covers the VPN layer directly. Partners adding DPP API integration still need to confirm their own downstream handling of exposure reports and opt-out records. That data passes through their product surface too.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Where_This_Fits_for_MSPs_Already_Running_VPN_Infrastructure\"><\/span><strong>Where This Fits for MSPs Already Running VPN Infrastructure<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p><a href=\"https:\/\/www.purevpn.com\/white-label\/?utm_medium=referral&amp;utm_source=aff-49383360&amp;utm_campaign=IA&amp;gateway=1&amp;aff=49383360&amp;data1=Cj0KCQjwjvfSBhDpARIsAEiOpSvaN_b4HGmTEaFVOnmJYdKmSthbjgkG0qpdtd8GqPZ6lxGP_I7Him4aAtlGEALw_wcB&amp;gad_source=1&amp;gad_campaignid=23995001013&amp;gbraid=0AAAABECb9ktrNc5wtfS0gq4pIre7DvK-I&amp;gclid=Cj0KCQjwjvfSBhDpARIsAEiOpSvaN_b4HGmTEaFVOnmJYdKmSthbjgkG0qpdtd8GqPZ6lxGP_I7Him4aAtlGEALw_wcB&amp;affiliate_id=49383360\">PureVPN White Label VPN Solution&#8217;s<\/a> data privacy protection layer covers identity exposure intelligence, dark web monitoring, and broker opt-out tracking. Coverage spans more than 400 brokers today, with over 150 partners already running it in production. MSPs access all three through documented endpoints and a shared partner account. Coverage and SLA terms get confirmed during technical review.<\/p>\n\n\n\n<p>MSPs already running PureVPN White Label VPN Solution&#8217;s VPN infrastructure add DPP API integration onto the same account. That avoids a second vendor relationship, a second contract, and a second support queue. Start with the <a href=\"https:\/\/www.purewl.com\/developer\/guides\/api\/\" target=\"_blank\" rel=\"noreferrer noopener\">API reference<\/a> to confirm whether an existing VPN account can support DPP API integration without rebuilding authentication.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_Thoughts\"><\/span>Final Thoughts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Two privacy products do not need two integration timelines. The account layer, the authentication model, and the partner relationship stay the same. This holds whether an MSP calls one surface or both. What changes is the endpoint set and the lifecycle each one tracks. MSPs that treat DPP API integration as an extension of an existing VPN account keep the evaluation scoped and simple.<\/p>\n\n\n\n<div class=\"wp-block-buttons text-center is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-1 wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link has-text-color has-background has-link-color wp-element-button\" href=\"https:\/\/www.purevpn.com\/white-label\/digital-privacy-protection\/\" style=\"color:#fdfafa;background-color:#b15aff\" target=\"_blank\" rel=\"noreferrer noopener\">Explore PureVPN&#8217;s White Label VPN Solution<\/a><\/div>\n<\/div>\n\n\n\n<link href=\"https:\/\/fonts.googleapis.com\/css2?family=Poppins:wght@500;600&#038;display=swap\" rel=\"stylesheet\">\n\n<style>\n  .faq-container {\n    font-family: 'Poppins', sans-serif;\n    max-width: 700px;\n    margin: 40px auto;\n    background: #F9F7FF;\n    border: 1px solid #D9D2F5;\n    border-radius: 18px;\n    box-shadow: 0 10px 30px rgba(166, 143, 239, 0.12);\n    padding: 30px;\n  }\n\n  .faq-title {\n    font-size: 20px;\n    font-weight: 600;\n    color: #4D3B7A;\n    margin-bottom: 20px;\n    text-align: center;\n  }\n\n  .faq-item {\n    background: #FFFFFF;\n    border: 1px solid #E2DAFA;\n    border-radius: 12px;\n    margin-bottom: 12px;\n    overflow: hidden;\n    box-shadow: 0 5px 20px rgba(166, 143, 239, 0.08);\n  }\n\n  .faq-question {\n    background: #F3EEFF;\n    padding: 15px;\n    cursor: pointer;\n    font-weight: 500;\n    color: #4D3B7A;\n    display: flex;\n    justify-content: space-between;\n    align-items: center;\n    font-size: 15px;\n  }\n\n  .faq-question:hover {\n    background: #EDE6FF;\n  }\n\n  .faq-answer {\n    display: none;\n    padding: 15px;\n    color: #5a4b85;\n    font-size: 14px;\n    line-height: 1.6;\n    border-top: 1px solid #E2DAFA;\n  }\n\n  .faq-icon {\n    font-weight: 600;\n    font-size: 18px;\n    transition: transform 0.3s ease;\n  }\n\n  .faq-item.active .faq-icon {\n    transform: rotate(45deg);\n  }\n<\/style>\n\n<div class=\"faq-container\">\n  <div class=\"faq-title\">Frequently Asked Questions<\/div>\n\n  <div class=\"faq-item\">\n    <div class=\"faq-question\">\n      Does DPP API integration require a second Secret Key?\n      <span class=\"faq-icon\">+<\/span>\n    <\/div>\n    <div class=\"faq-answer\">\n      No, both surfaces authenticate against the <strong>same partner account<\/strong>, though each session issues its own access token.\n    <\/div>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <div class=\"faq-question\">\n      Can a VPN account and an identity record be created in one API call?\n      <span class=\"faq-icon\">+<\/span>\n    <\/div>\n    <div class=\"faq-answer\">\n      No single endpoint creates both today, so a combined onboarding flow needs <strong>two parallel API calls<\/strong>.\n    <\/div>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <div class=\"faq-question\">\n      Does dark web monitoring use webhooks or polling?\n      <span class=\"faq-icon\">+<\/span>\n    <\/div>\n    <div class=\"faq-answer\">\n      Monitoring pushes a <strong>webhook<\/strong> when a registered asset reappears, while opt-out status runs on <strong>polling<\/strong> since brokers respond on their own timeline.\n    <\/div>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <div class=\"faq-question\">\n      How long does DPP API integration take for an MSP with an existing VPN integration?\n      <span class=\"faq-icon\">+<\/span>\n    <\/div>\n    <div class=\"faq-answer\">\n      Typically <strong>one to two sprints<\/strong>, since the authentication layer and partner account already exist.\n    <\/div>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <div class=\"faq-question\">\n      Who handles client communication if exposed data is found?\n      <span class=\"faq-icon\">+<\/span>\n    <\/div>\n    <div class=\"faq-answer\">\n      The <strong>infrastructure partner<\/strong> owns detection and opt-out mechanics, while the MSP owns communication inside its own product.\n    <\/div>\n  <\/div>\n<\/div>\n\n<script>\n  document.querySelectorAll('.faq-question').forEach(question => {\n    question.addEventListener('click', () => {\n      const item = question.parentElement;\n      const answer = question.nextElementSibling;\n      item.classList.toggle('active');\n\n      if (answer.style.display === 'block') {\n        answer.style.display = 'none';\n      } else {\n        document.querySelectorAll('.faq-answer').forEach(ans => ans.style.display = 'none');\n        document.querySelectorAll('.faq-item').forEach(it => it.classList.remove('active'));\n        item.classList.add('active');\n        answer.style.display = 'block';\n      }\n    });\n  });\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>Key Takeaways DPP API integration shares the VPN account&#8217;s authentication layer: both surfaces exchange the same Secret Key for a bearer access token under one partner account, so no second auth model or security review is needed. The two products track different lifecycles: VPN accounts move through create, enable, and renew states, while data privacy&#8230;<\/p>\n","protected":false},"author":14,"featured_media":7987,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[1009],"tags":[857],"class_list":["post-7986","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-privact-protection","tag-api-integration"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>DPP API Integration: Two Privacy Products, One Account - PureVPN White label<\/title>\n<meta name=\"description\" content=\"DPP API integration explained: how VPN account management and data privacy protection share one auth model and partner account.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DPP API Integration: Two Privacy Products, One Account - PureVPN White label\" \/>\n<meta property=\"og:description\" content=\"DPP API integration explained: how VPN account management and data privacy protection share one auth model and partner account.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/\" \/>\n<meta property=\"og:site_name\" content=\"PureVPN White label\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-04T06:55:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-04T06:55:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png\" \/>\n\t<meta property=\"og:image:width\" content=\"740\" \/>\n\t<meta property=\"og:image:height\" content=\"420\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"aiman.ikram\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"aiman.ikram\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/\",\"url\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/\",\"name\":\"DPP API Integration: Two Privacy Products, One Account - PureVPN White label\",\"isPartOf\":{\"@id\":\"https:\/\/www.purevpn.com\/white-label\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png\",\"datePublished\":\"2026-09-04T06:55:01+00:00\",\"dateModified\":\"2026-09-04T06:55:03+00:00\",\"author\":{\"@id\":\"https:\/\/www.purevpn.com\/white-label\/#\/schema\/person\/908f2967ccb959fc139728162444cf51\"},\"description\":\"DPP API integration explained: how VPN account management and data privacy protection share one auth model and partner account.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#primaryimage\",\"url\":\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png\",\"contentUrl\":\"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png\",\"width\":740,\"height\":420,\"caption\":\"Purple and white minimalist infographic showing API integration and data protection concepts.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.purevpn.com\/white-label\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"DPP API Integration: Two Privacy Products, One Account\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.purevpn.com\/white-label\/#website\",\"url\":\"https:\/\/www.purevpn.com\/white-label\/\",\"name\":\"PureVPN White Label\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.purevpn.com\/white-label\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.purevpn.com\/white-label\/#\/schema\/person\/908f2967ccb959fc139728162444cf51\",\"name\":\"aiman.ikram\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.purevpn.com\/white-label\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/708bd9d7ee9f229f0d91da03e894e2ce?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/708bd9d7ee9f229f0d91da03e894e2ce?s=96&d=mm&r=g\",\"caption\":\"aiman.ikram\"},\"url\":\"https:\/\/www.purevpn.com\/white-label\/author\/aiman-ikram\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DPP API Integration: Two Privacy Products, One Account - PureVPN White label","description":"DPP API integration explained: how VPN account management and data privacy protection share one auth model and partner account.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/","og_locale":"en_US","og_type":"article","og_title":"DPP API Integration: Two Privacy Products, One Account - PureVPN White label","og_description":"DPP API integration explained: how VPN account management and data privacy protection share one auth model and partner account.","og_url":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/","og_site_name":"PureVPN White label","article_published_time":"2026-09-04T06:55:01+00:00","article_modified_time":"2026-09-04T06:55:03+00:00","og_image":[{"width":740,"height":420,"url":"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png","type":"image\/png"}],"author":"aiman.ikram","twitter_card":"summary_large_image","twitter_misc":{"Written by":"aiman.ikram","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/","url":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/","name":"DPP API Integration: Two Privacy Products, One Account - PureVPN White label","isPartOf":{"@id":"https:\/\/www.purevpn.com\/white-label\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#primaryimage"},"image":{"@id":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#primaryimage"},"thumbnailUrl":"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png","datePublished":"2026-09-04T06:55:01+00:00","dateModified":"2026-09-04T06:55:03+00:00","author":{"@id":"https:\/\/www.purevpn.com\/white-label\/#\/schema\/person\/908f2967ccb959fc139728162444cf51"},"description":"DPP API integration explained: how VPN account management and data privacy protection share one auth model and partner account.","breadcrumb":{"@id":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#primaryimage","url":"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png","contentUrl":"https:\/\/d1jxermyrliwoo.cloudfront.net\/wp-content\/uploads\/2026\/07\/20105800\/Featured-Images-2026-07-20T152132.374.png","width":740,"height":420,"caption":"Purple and white minimalist infographic showing API integration and data protection concepts."},{"@type":"BreadcrumbList","@id":"https:\/\/www.purevpn.com\/white-label\/dpp-api-integration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.purevpn.com\/white-label\/"},{"@type":"ListItem","position":2,"name":"DPP API Integration: Two Privacy Products, One Account"}]},{"@type":"WebSite","@id":"https:\/\/www.purevpn.com\/white-label\/#website","url":"https:\/\/www.purevpn.com\/white-label\/","name":"PureVPN White Label","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.purevpn.com\/white-label\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.purevpn.com\/white-label\/#\/schema\/person\/908f2967ccb959fc139728162444cf51","name":"aiman.ikram","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.purevpn.com\/white-label\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/708bd9d7ee9f229f0d91da03e894e2ce?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/708bd9d7ee9f229f0d91da03e894e2ce?s=96&d=mm&r=g","caption":"aiman.ikram"},"url":"https:\/\/www.purevpn.com\/white-label\/author\/aiman-ikram\/"}]}},"_links":{"self":[{"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/posts\/7986","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/comments?post=7986"}],"version-history":[{"count":4,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/posts\/7986\/revisions"}],"predecessor-version":[{"id":8474,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/posts\/7986\/revisions\/8474"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/media\/7987"}],"wp:attachment":[{"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/media?parent=7986"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/categories?post=7986"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.purevpn.com\/white-label\/wp-json\/wp\/v2\/tags?post=7986"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}