Send a POST request with user_content in the body to receive the text with the personal data automatically detected and masked.
Detect And Mask Sensitive Data - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"flagged_content":"Contact me at *** or [email protected] (potential phone number detected)","masked_content":"Contact me at *** or [email protected]","notifications":"No inappropriate data submission detected"}
curl --location --request POST 'https://zylalabs.com/api/5392/privacy+guard+api/6985/detect+and+mask+sensitive+data' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"user_content": "Contact me at 123-456-7890 or [email protected]"
}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Send text with sensitive information; API automatically detects and maks personal data.
It is an API that protects the privacy of online users by automatically masking personal data.
Receives user content with possible personal data; returns text with masked sensitive information.
Customer care masking sensitive data in chats. Health applications that protect patient information. Social networks hiding private data in comments or posts.
Beside the number of API calls per month allowed, there are no other limitations.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
This endpoint returns two key fields: `flagged_content`, which shows the original text with detected sensitive data masked, and `masked_content`, which provides the text with all sensitive information redacted. Additionally, it includes `notifications` for any inappropriate data submissions detected.
The API can detect and mask various types of personal data, including names, addresses, phone numbers, social security numbers, and credit card information, across multiple formats such as text, images, and documents.
The response data is structured in JSON format, containing distinct fields: `flagged_content`, `masked_content`, and `notifications`. This organization allows users to easily identify the original and masked versions of the content.
The primary parameter for this endpoint is `user_content`, which should contain the text or data that may include sensitive information. Users can customize their requests by varying the content submitted for detection.
The API employs advanced recognition algorithms to ensure high accuracy in detecting sensitive data. Continuous updates and improvements to these algorithms help maintain data quality and reliability.
Common use cases include customer support interactions where sensitive data needs to be masked, telemedicine applications protecting patient information, and e-commerce platforms ensuring secure transactions by redacting personal details.
Users can utilize the `masked_content` to display safe text without exposing sensitive information, while `flagged_content` can help identify what was masked. This is useful for auditing and ensuring compliance with privacy regulations.
If the API returns partial or empty results, users should verify the input data for completeness and ensure it contains recognizable sensitive information. Adjusting the content or format may improve detection outcomes.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
811ms
Service Level:
83%
Response Time:
220ms
Service Level:
100%
Response Time:
581ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
214ms
Service Level:
100%
Response Time:
1,970ms
Service Level:
100%
Response Time:
608ms
Service Level:
100%
Response Time:
886ms
Service Level:
100%
Response Time:
1,774ms
Service Level:
100%
Response Time:
10,960ms
Service Level:
100%
Response Time:
1,113ms
Service Level:
100%
Response Time:
2,713ms
Service Level:
100%
Response Time:
349ms
Service Level:
100%
Response Time:
10,496ms
Service Level:
100%
Response Time:
554ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
750ms
Service Level:
100%
Response Time:
13,953ms
Service Level:
100%
Response Time:
4,733ms
Service Level:
100%
Response Time:
6,256ms