This guide takes you from a Secret Key to your first successful authenticated call against the PureWL DPP API.

Prerequisites

  • A PureWL partner account with API access enabled.
  • Your Secret Key, issued in the Reseller Dashboard / Partner Console. Keep it server-side only — never expose it in client-side code.

Get your Secret Key

Retrieve your Secret Key from the Partner Console. It authorizes every subsequent token exchange, so treat it like a password and never commit it to source control.

Exchange your Secret Key for an Access Token

POST your Secret Key to /auth/v2/accessToken using the secret grant type. The response returns an accessToken, its expiry (in seconds), and a refreshToken you can use to obtain a new Access Token later without re-sending the Secret Key. See Authentication for the full request/response reference.

Make your first authenticated call

Send the Access Token in the X-AccessToken request header on every authenticated call:
With a valid Access Token, make a safe read call — Get User — sending the token in the X-AccessToken header.

Interpret the response

Every response wraps its payload in a header object. header.response_code (and header.code, where present) equal 1 on success, with header.message giving a human-readable status. The actual data is in body.

Full example

Substitute <base_url> in the examples above with https://atomapi.com. See Base URL.

What next

Dark Web Monitoring

Look up breach records by email, phone, and other identifiers, and browse the breach catalog.

Data Broker Opt-Out

Scan data broker sites for a person and automate removal of their data.

User Management

Create and manage the users you protect with the DPP services.