Profil développeur Charles Anssens

Charles Anssens / Canssens

Allow you to analyze an email address, check validity, know if it is a personal email, a disposable email or a professional address.

5.9

103 ms

100%

Face Pixelate

Anonymise faces from a photo. Faces detected are pixelated. A filter could only pixelate faces depending of the detected age.

GPX Reducer

Reduce by resampling a GPX files. Up to 3x smaller file.

Identity generator

Create a virtual identity with fake personal data. Including birthdate, address, credit card number

7.6

190 ms

100%

		Title	Created at (Click to sort ascending)
A	1	Hello, Yes , with PRO, you get quota per 10k requests, If you do 10001 or 20000 you will pay 5+5 = 10$. If you plan to do more than +100k requests, you have the ULTRA plan. Feel free, to indicate your need, i could adapt the plans in function of your needs. Also I am thinking to add new api tools, to help customers to get more insight on the singularity of a webpage, for comparison/benchmarking. Any suggestion of improvements is welcome. Another remark , about throttling, feel free to indicate me your need. We deliver the service as continuous availability, if you need huge parallelization I could adapt the infrastructure. best regards,	목 8:42 20/7/23
A	3	Another point, maybe you should update your first post because it shows your api key.	월 9:03 3/1/22
A	3	Another point, maybe you should update your first post because it shows your api key.	월 9:03 3/1/22
A	6	Hello Matt, The error code are quite simple for the api : 400 if you don't give a good url to analyse 500 if it fails 200 if it is OK For other status code you could refer to RapidAPI that is our API gateway. For the moment we a two trade off to understand : we do a sequential API, you ask , we respond directly , but we need time to parse the url analysed (= the response time is quite slow). An another solution will be to acknowledge your request (response 200 without the result), perform the analyse, and then send you a call back with the result. the trade off for a sequential request is that we have to rate limit. I provided a new plan very generous but with a rate limit of max 1000 request/hour. So you have to manage a throttling. If you would like a solution without throttling, i will prefer to propose you a solution to get your request, and send you asynchronously the result with a callback. Regards.	목 9:47 23/12/21
A	6	Hello Matt, The error code are quite simple for the api : 400 if you don't give a good url to analyse 500 if it fails 200 if it is OK For other status code you could refer to RapidAPI that is our API gateway. For the moment we a two trade off to understand : we do a sequential API, you ask , we respond directly , but we need time to parse the url analysed (= the response time is quite slow). An another solution will be to acknowledge your request (response 200 without the result), perform the analyse, and then send you a call back with the result. the trade off for a sequential request is that we have to rate limit. I provided a new plan very generous but with a rate limit of max 1000 request/hour. So you have to manage a throttling. If you would like a solution without throttling, i will prefer to propose you a solution to get your request, and send you asynchronously the result with a callback. Regards.	목 9:47 23/12/21

Charles Anssens / Canssens

Discussions