Tanzania Location API

Tanzania Location API is a powerful tool that provides developers with a simple and efficient way to integrate location-based services into their applications.

About the API:  


Developers can use the Tanzania Location API  to create geolocation-based services that bring value to their users. For example, they can use the API to create transportation applications that match passengers with drivers based on their location. They can also use the API to create delivery services that accurately locate customers and deliver products to their doorstep.

Tanzania Location API  can also be used to create weather applications that provide users with accurate and up-to-date weather information based on their location. Developers can also use the API to create maps and navigation applications that provide users with turn-by-turn directions to their destination.

Tanzania Location API  is easy to integrate into existing applications and can be accessed via RESTful APIs. Developers can choose their preferred programming language, such as Java, Python, Ruby or PHP, and use the API to retrieve location data.

In addition to providing location data, this API also offers developers access to various location-based services, such as reverse geocoding. Reverse geocoding is the process of converting longitude and latitude coordinates into an address. Geofencing is the process of creating a virtual boundary around a specific location, and developers can use this feature to trigger location-based notifications, alerts or actions.

In conclusion, is a powerful tool for developers who want to create location-based services for the Tanzania market. The API provides accurate and up-to-date location data, as well as access to a wide variety of location-based services and advanced features. With the Tanzania Location API, developers can create innovative and useful applications that deliver value to users and drive business growth.

 

What this API receives and what your API provides (input/output)?

It will receive parameters and provide you with a JSON.

 

What are the most common uses cases of this API?

  1. Cab services: Developers can use the Tanzania Location API  to provide destination information for drivers and passengers of the transportation service.

  2. Delivery services: Can be used to track the location of delivery drivers and optimize delivery routes to save time and fuel costs.

  3. E-commerce: Tanzania Location API  can be used to verify delivery addresses.

  4. Real Estate:Can be used to provide location-based property listings.

  5. Advertising and marketing: Can be used to deliver location-based advertising and marketing campaigns to users.

 

Are there any limitations to your plans?

Besides the number of API calls, there is no other limitation.

API Documentation

Endpoints


To use this endpoint you must indicate the latitude and longitude of the 2 locations and the type of distance measurement km, mi, yd and ft.



                                                                            
GET https://www.zylalabs.com/api/1938/tanzania+location+api/1672/get+tanzania+distance
                                                                            
                                                                        

Get Tanzania distance - Endpoint Features

Object Description
lat1 [Required]
lon1 [Required]
lat2 [Required]
lon2 [Required]
unit [Optional]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {
  "distance": "621.04km",
  "duration": "8h 6min",
  "unit": "km"
}
                                                                                                                                                                                                                    
                                                                                                    

Get Tanzania distance - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/1938/tanzania+location+api/1672/get+tanzania+distance?lat1=-3.3696824&lon1=36.6880791&lat2=-6.7785163&lon2=39.2694781&unit=km' --header 'Authorization: Bearer YOUR_API_KEY' 

    

To use this endpoint all you have to do is to insert in the parameters the latitude, longitude of 2 locations with their unit of measure km and mi.



                                                                            
GET https://www.zylalabs.com/api/1938/tanzania+location+api/1673/get+tanzania+route
                                                                            
                                                                        

Get Tanzania route - Endpoint Features

Object Description
start_lat [Required]
start_lon [Required]
end_lat [Required]
end_lon [Required]
distance_unit [Optional]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {
  "distance": "621.04km",
  "duration": "8h 6min",
  "steps": [
    {
      "direction": "depart",
      "distance": "0.11km",
      "duration": "0min:15s",
      "instruction": "",
      "location": [
        36.687858,
        -3.369553
      ]
    },
    {
      "direction": "exit rotary",
      "distance": "0.43km",
      "duration": "1min:7s",
      "instruction": "",
      "location": [
        36.688282,
        -3.36991
      ]
    },
    {
      "direction": "end of road",
      "distance": "0.65km",
      "duration": "0min:39s",
      "instruction": "",
      "location": [
        36.688578,
        -3.373778
      ]
    },
    {
      "direction": "rotary",
      "distance": "0.08km",
      "duration": "0min:8s",
      "instruction": "",
      "location": [
        36.694211,
        -3.372425
      ]
    },
    {
      "direction": "exit rotary",
      "distance": "1.07km",
      "duration": "0min:59s",
      "instruction": "",
      "location": [
        36.694575,
        -3.372422
      ]
    },
    {
      "direction": "rotary",
      "distance": "0.01km",
      "duration": "0min:0s",
      "instruction": "",
      "location": [
        36.702964,
        -3.377172
      ]
    },
    {
      "direction": "exit rotary",
      "distance": "0.04km",
      "duration": "0min:2s",
      "instruction": "",
      "location": [
        36.703016,
        -3.377153
      ]
    },
    {
      "direction": "new name",
      "distance": "1.32km",
      "duration": "1min:12s",
      "instruction": "",
      "location": [
        36.70326,
        -3.376829
      ]
    },
    {
      "direction": "end of road",
      "distance": "75.30km",
      "duration": "1h 16min",
      "instruction": "",
      "location": [
        36.707497,
        -3.36571
      ]
    },
    {
      "direction": "roundabout",
      "distance": "0.06km",
      "duration": "0min:2s",
      "instruction": "",
      "location": [
        37.335863,
        -3.346261
      ]
    },
    {
      "direction": "exit roundabout",
      "distance": "0.91km",
      "duration": "1min:19s",
      "instruction": "",
      "location": [
        37.336347,
        -3.34614
      ]
    },
    {
      "direction": "rotary",
      "distance": "0.05km",
      "duration": "0min:1s",
      "instruction": "",
      "location": [
        37.343834,
        -3.343011
      ]
    },
    {
      "direction": "exit rotary",
      "distance": "21.15km",
      "duration": "14min:55s",
      "instruction": "",
      "location": [
        37.34415,
        -3.342845
      ]
    },
    {
      "direction": "turn",
      "distance": "1.01km",
      "duration": "0min:43s",
      "instruction": "",
      "location": [
        37.513023,
        -3.409095
      ]
    },
    {
      "direction": "turn",
      "distance": "239.27km",
      "duration": "3h 8min",
      "instruction": "",
      "location": [
        37.521054,
        -3.405406
      ]
    },
    {
      "direction": "turn",
      "distance": "0.58km",
      "duration": "0min:24s",
      "instruction": "",
      "location": [
        38.462045,
        -5.163851
      ]
    },
    {
      "direction": "roundabout",
      "distance": "0.01km",
      "duration": "0min:0s",
      "instruction": "",
      "location": [
        38.46318,
        -5.168792
      ]
    },
    {
      "direction": "exit roundabout",
      "distance": "20.67km",
      "duration": "14min:34s",
      "instruction": "",
      "location": [
        38.463239,
        -5.168834
      ]
    },
    {
      "direction": "roundabout",
      "distance": "0.04km",
      "duration": "0min:1s",
      "instruction": "",
      "location": [
        38.554142,
        -5.323944
      ]
    },
    {
      "direction": "exit roundabout",
      "distance": "136.00km",
      "duration": "1h 36min",
      "instruction": "",
      "location": [
        38.554241,
        -5.324173
      ]
    },
    {
      "direction": "turn",
      "distance": "58.02km",
      "duration": "41min:0s",
      "instruction": "",
      "location": [
        38.389774,
        -6.332919
      ]
    },
    {
      "direction": "end of road",
      "distance": "4.84km",
      "duration": "3min:25s",
      "instruction": "",
      "location": [
        38.86792,
        -6.471513
      ]
    },
    {
      "direction": "roundabout",
      "distance": "0.06km",
      "duration": "0min:2s",
      "instruction": "",
      "location": [
        38.907354,
        -6.457358
      ]
    },
    {
      "direction": "exit roundabout",
      "distance": "46.76km",
      "duration": "33min:6s",
      "instruction": "",
      "location": [
        38.907657,
        -6.457518
      ]
    },
    {
      "direction": "turn",
      "distance": "1.59km",
      "duration": "1min:28s",
      "instruction": "",
      "location": [
        39.207135,
        -6.700812
      ]
    },
    {
      "direction": "roundabout",
      "distance": "0.05km",
      "duration": "0min:3s",
      "instruction": "",
      "location": [
        39.221284,
        -6.701852
      ]
    },
    {
      "direction": "exit roundabout",
      "distance": "1.44km",
      "duration": "1min:19s",
      "instruction": "",
      "location": [
        39.221436,
        -6.702118
      ]
    },
    {
      "direction": "new name",
      "distance": "1.85km",
      "duration": "1min:42s",
      "instruction": "",
      "location": [
        39.229155,
        -6.711934
      ]
    },
    {
      "direction": "new name",
      "distance": "1.64km",
      "duration": "1min:31s",
      "instruction": "",
      "location": [
        39.232408,
        -6.727699
      ]
    },
    {
      "direction": "roundabout",
      "distance": "0.04km",
      "duration": "0min:2s",
      "instruction": "",
      "location": [
        39.237116,
        -6.741512
      ]
    },
    {
      "direction": "exit roundabout",
      "distance": "1.27km",
      "duration": "1min:10s",
      "instruction": "",
      "location": [
        39.237183,
        -6.741782
      ]
    },
    {
      "direction": "new name",
      "distance": "2.08km",
      "duration": "1min:55s",
      "instruction": "",
      "location": [
        39.24276,
        -6.751556
      ]
    },
    {
      "direction": "new name",
      "distance": "0.74km",
      "duration": "0min:40s",
      "instruction": "",
      "location": [
        39.256866,
        -6.763761
      ]
    },
    {
      "direction": "new name",
      "distance": "0.94km",
      "duration": "0min:52s",
      "instruction": "",
      "location": [
        39.261704,
        -6.76813
      ]
    },
    {
      "direction": "new name",
      "distance": "0.18km",
      "duration": "0min:17s",
      "instruction": "",
      "location": [
        39.263945,
        -6.77552
      ]
    },
    {
      "direction": "turn",
      "distance": "0.71km",
      "duration": "0min:33s",
      "instruction": "",
      "location": [
        39.26388,
        -6.777141
      ]
    },
    {
      "direction": "turn",
      "distance": "0.03km",
      "duration": "0min:5s",
      "instruction": "",
      "location": [
        39.270168,
        -6.77833
      ]
    },
    {
      "direction": "turn",
      "distance": "0.06km",
      "duration": "0min:13s",
      "instruction": "",
      "location": [
        39.270022,
        -6.778569
      ]
    },
    {
      "direction": "arrive",
      "distance": "0.00km",
      "duration": "0min:0s",
      "instruction": "",
      "location": [
        39.269539,
        -6.778369
      ]
    }
  ]
}
                                                                                                                                                                                                                    
                                                                                                    

Get Tanzania route - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/1938/tanzania+location+api/1673/get+tanzania+route?start_lat=-3.3696824&start_lon=36.6880791&end_lat=-6.7785163&end_lon=39.26947841&distance_unit=km' --header 'Authorization: Bearer YOUR_API_KEY' 

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Tanzania Location API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
100%
 Response Time
1,130ms

Category:


Related APIs