Get Started
Register your App
You surely hate nasty annoying bots just as much as we do. So you'll understand why we ask you to register every app you create — we want to make sure that our API is only used to build awesome products for our community.
It won't take long anyway. We'll ask you to provide a few details including the name and a description of your app, as well as the permissions that the user will need to grant in order to use it.
To use the API, you'll need to agree to our API Service Terms and Conditions — we promise that they're friendly and easy to read, so make sure you look them over before you register.
Your Application Key
Once you've registered your app (and got us super excited because we can't wait to see what you're creating there), you'll get an application key. It's a unique code that allows you to connect with our API.
You can always find all your registered applications in the "Manage your apps" page.
⚠️ Remember to keep the key secret — you don't want other people to use the API on your behalf!
If you're not going to build an app that requires users to log in, and want to access the API directly yourself, you can simply create a personal token.
Authenticating Users
With the old API, authentication was a bit of a pain. Users had to go to Manob.Ai Market, log in, retrieve an API key and then copy-paste it into your app.
Not anymore! 🎉
With the new API, users will be redirected from your app to a login page that we will provide. Once they have successfully logged in, we'll send them back to the app. If it's the first time they've logged in to your app, they will also have to grant the permissions your app requires.
You can find more detailed info about the whole OAuth flow below.
Share Your Work
Once you've created your app, you'll surely want to let our community know that there's a new neat product to help them make the most out of Manob.Ai Market.
Shoot us the link, and we'll showcase it on our Market Blog!
Rate Limiting
All requests to the Manob.Ai API are dynamically rate limited. As such are unable to provide static values as these will vary between clients. To determine when we enforce these rate limits we use a combination of factors, including, but not limited to:
- Number of previously made requests
- Requested endpoint: Some endpoints require more resources and are more tightly rate-limited.
- Client IP reputation
If you do manage to cross the acceptable number of requests you are permitted to make, you will receive a HTTP 429 response. Included in this response is a HTTP header Retry-After that will denote in seconds how long you have to wait until you're able to make requests again. It's important that if you're building automated systems to make requests on your behalf, that you take this into account and handle this scenario gracefully in your application.