Introducing JSONREPO

Why build/use an API integration service?

JSONREPO aims to solve a major pain point that a lot of us developers have, namely API integrations. In order to build, run and maintain applications, we often rely on third party API integrations to help us accomplish tasks that would otherwise take a lot of time and effort to solve for.

A lot of APIs that are being offered today by third party vendors are fragmented. They rarely follow the same standards and you often find yourself connecting to, and paying for, more than you need. Additionally, you often have to manage separate account credentials, connection protocols, 3rd party library/SDK loading, and so much more.

This is the problem we aims to solve for. A single service that provides an ever increasing number of APIs for you to use. One API to rule them all.

Using JSONREPO

Using our service is super easy. Simply fire a normal HTTPs request to our servers using any client or programming language of choice (curl is used for demonstration) detailing your intent and we'll take care of the rest.

Example use-case:

Say that you want to build an application that allows users to signup using an email account. One problem you might run into is that potential abusers of your service may signup with disposable emails to perpetually get access to your free tier plan. To mitigate for this, you can simply integrate with our disposable email API checker to mitigate for these cases.

// Check if an email comes from a registered disposable email provider

curl -G \
https://api.jsonrepo.com/v1/compute/validator/email \
-H "api_key: {YOUR_API_KEY_HERE}" \
--data-urlencode "email=some_email@evil-provider.com" 

Our API endpoint will reply with the following:

// Server Response

{
    "http_code": 200,
    "http_message": "Ok",
    "message": "Successful execution",
    "payload": {
        "email": {
            "input": "some_email@evil-provider.com",
            "domain": "evil-provider.com",
            "is_valid": true,
            "is_disposable": true
        }
    }
}

Now that the email is flagged as is_disposable = true you can simply reject it.

What APIs does JSONREPO provide?

We generally segment our APIs based on class. Currently, there are two distinct classes that we support (with more to come). The first is Knowledge APIs and the second is Compute APIs.

The Knowledge class revolves around data lookup. Our database contains hundreds of gigabytes of structured data ready to be queried. You can lookup Books, TV Shows & Movies, Nutritional values, Cooking Recipes and so much more. We're constantly working on adding new APIs for you to consume and build applications around.

The Compute class is all about generation and verification. We offer endpoints that will help you verify phone numbers, check disposable emails, parse user agent strings, calculate distances and a whole lot more.

Our catalogue keeps expanding based on user demands. If you find yourself in need of an API endpoint, contact us and let us know. If possible, we'll add it to our offering free of charge. Our ambition is as stated earlier: One API to rule them all

Quick Links

To find out more about our API endpoints and how to implement them, check out our documentation.

If you need to get in touch with us, feel free to shoot us a message using any of the following channels: Twitter, Discord or Email.

Happy Coding!

// The JSONREPO Team