API usage and pricing clarification
General information about our pricing
Our pricing is subscription based. You can purchase a plan that fits your requirements which implies a monthly fee. We offer a number of plans out of the box. You can find an overview about these plan on our pricing page. If none of these plans fit your requirements, you probably need a custom plan that you need to negotiate with us directly. Please contact us in this case. When you purchase a plan, you purchase both request limits (in terms of maximum locations and vehicles) and a number of daily calls. calls are Barikoi's currency, i.e. you can spend these calls for whatever API you like. However, costs for each request are dependent on the API you use. To understand the differences, we recommend you to read "What is one call?".
API usage and pricing clarification
A single API request and a single API call are not always the same. A single API request to the server might call multiple APIs. An API might depend on other internal APIs to deliver the desired response. The number of call depends on the number of parameters of a request and the number of internal API calls needed to make to provide the desired response. For instance, A single request to Rupantor API results in two API calls since Rupantor API uses geocode API to operate. Routing API follows the same formalities as Rupantor.
API call count for each request
Reverse Geocode API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 1 | | Post_code | 1 | | country | 1 | | sub_district | 1 |
| | | Parameter | Call count |
|---|
| address | 1 | | Union | 1 | | Pouroshova | 1 | | location_type | 1 | | division | 1 |
| | | Parameter | Call count |
|---|
| area | 1 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Reverse Geocoding API(server)
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 1 | | Post_code | 1 | | country | 1 | | sub_district | 1 |
| | | API | Call count |
|---|
| address | 1 | | Union | 1 | | Pouroshova | 1 | | location_type | 1 | | division | 1 |
| | | Parameter | Call count |
|---|
| area | 1 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Geocoding API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Autocomplete API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Autocomplete API with city filter
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Post Office autocomplete API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 1 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Industrial autocomplete API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Bangla autocomplete API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 1 | | match | 0 |
|
Distance API
| Parameter | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | Parameter | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | Parameter | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Rupantor geocoder API
| API | Call count |
|---|
| Base Count | 2 | | District | 1 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | API | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 1 | | bangla | 1 | | match | 0 |
|
Routing API
| API | Call count |
|---|
| Base Count | 2 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | API | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Route optimization API
| API | Call count |
|---|
| Base Count | 1 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | API | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Nearest API
| API | Call count |
|---|
| Base Count | 2 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | API | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
Route Match API
| API | Call count |
|---|
| Base Count | 2 | | District | 0 | | Post_code | 0 | | country | 0 | | sub_district | 0 |
| | | API | Call count |
|---|
| address | 0 | | Union | 0 | | Pouroshova | 0 | | location_type | 0 | | division | 0 |
| | | API | Call count |
|---|
| area | 0 | | post_office | 0 | | Thana | 0 | | bangla | 0 | | match | 0 |
|
What happens when i go over the call limit
If you go over the daily/monthly call limit your API key will not stop working immediately and you'll get an Email. If this happens frequently, we'll contact you to discuss this. If you go far beyond this daily limit then there is a hard limit to protect our platform from abuse.
Please note that there is also a (permissive) minutely call limit specified in our documentation, which is not reported via Email. If that limit is exceeded you get a bad request (http code 429) and need to delay you requests or buy a bigger package. Currently, this is also a soft limit and we block requests only if you go too much beyond it.
Billing Cycle
Default billing cycle start from the day an API key is generated and billed 29 days from the API generation date. The cycle is changeable according to users convenience.