JSON queries

Request

GET https://<aliastoken>.yoursafe.id/?json=1

Response

Returns a JSON object with account status and compliance-related metadata.

{
      "aliastoken": "xyz123.yoursafe.id",
      "accountstatus": "active",
      "country": "Netherlands",
      "countrycode": "NL",
      "eighteenplus": true,
      "idverifieddate": "2022-07-21T06:27:33Z",
      "peplistdate": "2023-05-24T10:41:38Z",
      "sanctiondate": "2023-05-24T10:41:38Z",
      "uksanctionlists": "Negative",
      "unsanctionlists": "Negative",
      "ussanctionlists": "Negative",
      "eusanctionlists": "Negative",
      "ibanserials": ["a8999c4cbf0a1a67a3d0d4cf9cb7ea2b9a7d66301a93941f9ac2079597de39e1"]
    }

JSON query reliability

Integrate JSON queries server-side, validate field types, and handle transient endpoint/network failures with retries.

Response field reference

aliastoken: Token identifier, usually <token>.yoursafe.id.
aliasserial: Serial that changes when significant alias/account data changes.
accountstatus: Current account state, typically active or inactive.
country, countrycode: Country details using ISO-3166 for countrycode.
eighteenplus: Boolean indicating whether the user is over 18.
idverifieddate: Last ID verification timestamp in UTC ISO-8601 format.
peplistdate, sanctiondate: Latest compliance screening timestamps.
uk/uns/us/eusanctionlists: Sanction list indicators, commonly Negative.
ibanserials: Array of serials related to associated IBANs.

Implementation checklist

Use backend-to-backend HTTPS calls and avoid exposing raw responses directly to clients.
Validate field presence and type before making compliance decisions.
Handle temporary network or endpoint failures with retries and graceful degradation.
Track serial/timestamp changes to trigger re-checks in your onboarding or monitoring flows.

DNS queries

Look up a single alias-token field from a DNS TXT record.