We use cookies (just for analytics) on this website. If you continue we will assume you are happy with it. ok


Back to index

Getting started with the BeBanjo APIs

If you are new and looking to integrate with BeBanjo’s products using our APIs, we will get you up to speed in no time. This is what you have to do.

First, you should read the introduction to REST APIs where you can learn about the principles behind our APIs and conventions we use, and how to authenticate API users. These guides will help you get access to our APIs from your code.

If you know about all these things already, you can jump straight to:

You probably want to have a rock-solid codebase. To achieve that you should always check for responses from the APIs and errors. We have a guide just for that: Status codes and errors.

After all that you can find out more about API resources (what parameters are valid, which are required and which optional, etc.) in this same documentation for Movida / Metadata and Sequence.

When building an application that invokes the BeBanjo APIs, please use the BeBanjo staging and pre-production environments, before hitting the BeBanjo production environment. This lets you safely build and test functionality, as well as ascertain performance and security. Please speak to your Technical Account Manager to get access to the staging and pre-production environments.

Finally, if you need any help please speak to your Technical Account Manager.

API usage guidelines

BeBanjo does not currently enforce a rate limit for server-to-server requests but to help clients comply with the BeBanjo API terms we recommend limiting your usage to 5,000 requests per hour across the Movida and Sequence APIs, with no more than 20 concurrent requests per second.

If you think your integrations will exceed these guidelines please speak with your Technical Account Manager to review your requirements; this may mean that rate limiting is enabled for your integrations and they’ll need to be able to handle a 429 status code (and Ratelimit-Reset response header).

Please hit the BeBanjo staging and pre-production environments with a representative data load, in order to check for performance, before deploying to production. Your Technical Account Manager can give you access and help you plan.

The various API endpoints have different performance characteristics and we understand clients use the APIs for different purposes meaning that a higher number of requests per minute is often not problematic.

Last updated October 06th, 2021.