One real request. One real result.
Use the API or supported integration surface to replace identifiers before content reaches downstream systems that do not require the originals.
curl https://api.pseudonymize.io/v1/text \
-H "Authorization: Bearer $PS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"text": "Alice lives in Munich",
"policy": "default"
}'
{
"text": "PERSON_01 lives in LOCATION_01",
"entities": [
{ "type": "PERSON", "original": "Alice", "pseudonym": "PERSON_01" },
{ "type": "LOCATION", "original": "Munich", "pseudonym": "LOCATION_01" }
]
}
-H "Authorization: Bearer $PS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"text": "Alice lives in Munich",
"policy": "default"
}'
{
"text": "PERSON_01 lives in LOCATION_01",
"entities": [
{ "type": "PERSON", "original": "Alice", "pseudonym": "PERSON_01" },
{ "type": "LOCATION", "original": "Munich", "pseudonym": "LOCATION_01" }
]
}
01
Authentication
Bearer token authentication via HTTP headers.
02
Supported inputs
Raw text strings and JSON payloads.
03
Handle processing states explicitly.
Standard HTTP 4xx/5xx status codes with detailed JSON error messages.
04
SDKs
Python package available (pip install pseudonymize). Standard HTTP integrations for Node.js, Go, Python, and cURL.
pip install pseudonymize