Sends a POST request with content_metadata and user_data in the body.The API responds with filtered, age-appropriate content.
Filter Content By Age - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"age_appropriate_content":["Video A"],"alerts":"No alerts for this user","alternative_suggestions":"No restrictions apply"}
curl --location --request POST 'https://zylalabs.com/api/5398/content+age+filter+api/6991/filter+content+by+age' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"content_metadata": [
"Video A",
"Blog B"
],
"user_data": {
"age": 12
}
}'
| 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 user data and content metadata to receive age-based content filtering.
It is an API that classifies and restricts content according to the user's age, ensuring a safe online experience.
Receives content metadata and user age data; returns age-appropriate filtered content.
Educational platforms that adapt content to age. Entertainment apps that limit inappropriate content. Social networks that protect young users from sensitive content.
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.
The Filter Content By Age endpoint returns a JSON object containing age-appropriate content, alerts for the user, and alternative suggestions. For example, it may return filtered content like `{"age_appropriate_content":["Video A"],"alerts":"No alerts for this user","alternative_suggestions":"No restrictions apply"}`.
The key fields in the response data include `age_appropriate_content`, which lists suitable content, `alerts`, indicating any warnings for the user, and `alternative_suggestions`, which provides options if restrictions apply.
The response data is organized in a structured JSON format. It includes an array for age-appropriate content, and string fields for alerts and alternative suggestions, making it easy to parse and utilize in applications.
The endpoint accepts parameters such as `content_metadata`, which includes details about the content, and `user_data`, which contains information about the user's age and preferences, allowing for tailored filtering.
Users can customize their requests by providing specific `content_metadata` that describes the content type and `user_data` that reflects the user's age group, enabling more precise filtering based on individual needs.
The API utilizes a combination of content classification algorithms and databases that categorize digital content based on age appropriateness, ensuring that the filtering is based on reliable and up-to-date information.
Data accuracy is maintained through continuous updates to the content classification algorithms and regular audits of the content databases, ensuring that the filtering aligns with current age-appropriate standards and regulations.
Typical use cases include educational platforms that tailor learning materials to different age groups, entertainment apps that restrict access to mature content, and social networks that safeguard young users from inappropriate interactions.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
83%
Response Time:
215ms
Service Level:
100%
Response Time:
227ms
Service Level:
100%
Response Time:
282ms
Service Level:
100%
Response Time:
478ms
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
431ms
Service Level:
100%
Response Time:
444ms
Service Level:
100%
Response Time:
929ms
Service Level:
100%
Response Time:
840ms
Service Level:
100%
Response Time:
241ms
Service Level:
100%
Response Time:
1,320ms
Service Level:
100%
Response Time:
764ms
Service Level:
100%
Response Time:
1,301ms
Service Level:
100%
Response Time:
4,681ms
Service Level:
100%
Response Time:
801ms
Service Level:
100%
Response Time:
881ms
Service Level:
100%
Response Time:
2,312ms
Service Level:
100%
Response Time:
902ms
Service Level:
100%
Response Time:
2,346ms
Service Level:
100%
Response Time:
3,519ms