- Home
- Location Intelligence Software
- LocationAPI
LocationAPI
The contact page lists an address in Jubilee Hills, Hyderabad, Telangana, India.
What it is
LocationAPI estimates locations for connected devices using visible cellular towers and WiFi networks, without requiring GPS. Its Geolocation API applies location data, datasets, and algorithms to IoT, M2M, and other connected devices, with described worldwide reach. Requests are JSON POSTs sent to a regional endpoint. Documentation includes cURL, PHP, Python, and JavaScript examples, as well as an interactive sandbox. A request can include up to 7 cells and 15 WiFi objects. WiFi positioning is enabled only for eligible deployments based on region and intended use. Accuracy depends on source and location: the FAQ gives cell estimates around 450 metres in urban areas and 1500 metres in rural areas, and WiFi estimates around 25–50 metres in urban areas and 50–150 metres in rural areas. The Developer plan costs nothing, has daily and monthly request limits, and is marked for no commercial use. Business pricing is priced on request, with usage options based on project needs. The documentation recommends scoped tokens, stored server-side and rotated regularly. Several other products on this platform are being phased out, with new integrations directed to LocationIQ.
For and against
For
- Works from cellular and WiFi signals without GPS.
- Provides examples in four programming languages.
- Includes an interactive API sandbox.
- Request limit permits up to 7 cells and 15 WiFi objects.
Against
- Developer plan has request limits and no commercial use.
- WiFi positioning depends on region and intended use.
- Geocoding, Timezone, Maps, and Static Maps are being phased out.
The verdict
LocationAPI offers a way to estimate connected-device locations through an API, with examples and a sandbox to support integration. Check accuracy expectations, eligibility for WiFi positioning, and the Developer plan's restrictions before relying on it.
Who it suits
LocationAPI may suit developers locating connected devices when GPS is not required. Its free plan is restricted to non-commercial use, while WiFi positioning depends on deployment eligibility.
Plans and prices
Developer
limited requests · no commercial use · email support
Read 8 Oct 2026 · unwiredlabs.com
Business
scale to millions of requests · custom SLA & Contracts
Read 8 Oct 2026 · unwiredlabs.com
On the record
- Accuracy guidance
- The FAQ says typical accuracy varies by data source and location, with cell-based results around 450 metres in urban areas and 1500 metres in rural areas, and WiFi-based results around 25–50 metres in urban areas and 50–150 metres in rural areas.unwiredlabs.com · read 8 Oct 2026
- API integration
- Requests to the Geolocation API are sent as JSON POST requests to a regional endpoint.docs.unwiredlabs.com · read 8 Oct 2026
- Code examples
- The documentation provides ready-made cURL, PHP, Python, and JavaScript examples and an interactive sandbox.docs.unwiredlabs.com · read 8 Oct 2026
- Commercial use
- The Developer plan is labeled “no commerical use.”unwiredlabs.com · read 8 Oct 2026
- Global reach
- The Geolocation API is described as locating IoT, M2M, and other connected devices anywhere in the world.docs.unwiredlabs.com · read 8 Oct 2026
- Location sources
- The Geolocation API uses cellular and WiFi data, datasets, and algorithms to calculate device locations.docs.unwiredlabs.com · read 8 Oct 2026
- Pricing limits
- Free Developer Plans have daily and monthly request limits; Business Plans offer flexible usage options based on project needs.unwiredlabs.com · read 8 Oct 2026
- Purpose
- LocationAPI locates connected devices from visible cell towers and WiFi networks without needing GPS.docs.unwiredlabs.com · read 8 Oct 2026
- Request limits
- A request can include up to 7 cells and 15 WiFi objects.docs.unwiredlabs.com · read 8 Oct 2026
- Security
- The documentation recommends scoped access tokens, keeping tokens server-side, and rotating them regularly.docs.unwiredlabs.com · read 8 Oct 2026
- Sunsetting products
- Geocoding, Timezone, Maps, and Static Maps are being phased out on this platform, and new integrations are directed to LocationIQ.docs.unwiredlabs.com · read 8 Oct 2026
- Support
- The FAQ says the company aims to reply to every query within one business day and offers dedicated support plans for enterprise customers.unwiredlabs.com · read 8 Oct 2026
- WiFi eligibility
- WiFi positioning is enabled for eligible deployments based on region and intended use.docs.unwiredlabs.com · read 8 Oct 2026
The review
LocationAPI estimates connected-device positions from cellular and WiFi signals, without GPS. It best suits developers adding location lookup to IoT or M2M services. Its code examples and sandbox support integration, but accuracy expectations, WiFi eligibility, and commercial-use limits shape whether it fits a project.
Overview
The API combines cell and WiFi data with datasets and algorithms to calculate a device location. Requests are JSON POSTs to a regional endpoint, with up to seven cells and 15 WiFi objects per request. The service describes coverage for connected devices worldwide, which may suit deployments that cannot rely on GPS. That broad reach comes with variable precision: typical cell-based results are around 450 metres in urban areas and 1,500 metres in rural areas. WiFi-based results are typically around 25–50 metres in urban areas and 50–150 metres in rural areas.
Those ranges make LocationAPI a better fit for approximate positioning than applications that depend on a precise location in every setting. WiFi positioning is enabled only for eligible deployments, based on region and intended use, so teams should not assume the closer estimates will be available to them.
Key features
Ready-made cURL, PHP, Python, and JavaScript examples and an interactive sandbox give developers concrete ways to start integrating the API. The request format and object limits make the interface specific enough to plan around, though the offering is focused on location lookup rather than drive-time analysis, territory planning, or demographic data.
The documentation recommends scoped access tokens, keeping tokens server-side, and rotating them regularly. That guidance matters because the API depends on credentials in application requests; following it helps reduce the risk of exposing tokens through client code or leaving them unchanged indefinitely.
Geocoding, Timezone, Maps, and Static Maps are being phased out on this platform, and new integrations for those products are directed to LocationIQ. LocationAPI remains relevant for device positioning, but teams seeking those other capabilities should plan around the transition.
Pricing
The Developer plan is free. It includes limited requests and email support, but prohibits commercial use and applies daily and monthly request limits. It is appropriate for noncommercial evaluation or a small integration that stays within its caps; it is not a route to production use for a commercial service.
The Business plan is priced on request, billed as low as $0.10 /device. It offers flexible usage that can scale to millions of requests, with custom SLAs and contracts. That makes it the relevant option for commercial deployments whose demand exceeds the Developer limits, though teams should account for the per-device pricing and agree on the terms that fit their project.
A free trial is available. Support aims to answer every query within one business day, while enterprise customers can obtain dedicated support plans.
Platforms
LocationAPI supports Android, API, and web. Its central integration path is the API, with language examples for cURL, PHP, Python, and JavaScript.
Who it's for
LocationAPI suits developers and organizations that need to estimate locations for connected devices, especially IoT or M2M deployments where GPS is unavailable or unsuitable. It is a stronger fit when approximate positioning is acceptable and the deployment qualifies for the desired signal sources. Projects requiring commercial use need the Business plan; those needing location intelligence beyond device lookup should consider a broader tool.
Pros and cons
- Pros: The API supports up to seven cells and 15 WiFi objects per request, and ready-made examples plus a sandbox help developers get started.
- Pros: Typical WiFi estimates are closer than cell-based estimates, making WiFi positioning useful where the deployment is eligible and that added precision matters.
- Cons: WiFi positioning depends on region and intended use, so teams cannot count on it in every deployment.
- Cons: The free Developer plan has daily and monthly caps and bars commercial use, limiting its role to noncommercial use and evaluation.
- Cons: Cell-based estimates can be around 1,500 metres in rural areas, which is too coarse for applications needing close location accuracy.
Alternatives
For location intelligence options, browse Location Intelligence Software. Choose Crowd Connected if you need a freemium option with a free plan that includes one floorplan, unlimited area, and unlimited MAUs. Mapbox Studio is another freemium option with a free plan for Mapbox users, though related API and custom tileset usage may be billed separately.
Sitewise Analytics may suit teams looking for curated geospatial variables and preset trade-area options; its Market Grid plan requires a Sitewise account. Stadia Maps offers a free tier with 200,000 credits per month and no additional usage, or a Starter plan at $20 a month for 1,000,000 credits per month. Azure Maps is worth considering for its free Gen2 tier, which includes free transactions across data, geolocation, search, spatial calculations, and imagery services.
NIQ, Maptive, and Kalibrate Location Intelligence are also alternatives to compare.
Verdict
Choose LocationAPI when your project needs a focused way to estimate connected-device locations and can accommodate its accuracy ranges and conditional WiFi access. Its examples and sandbox support integration, while the Developer plan gives noncommercial users a free entry point. Look elsewhere if commercial use must stay free, if rural cell estimates are too coarse, or if the project needs mapping and planning capabilities beyond device positioning.