Zone-check API for businesses
With an API key, you can call DroMap's flight check engine from your own systems and apps. Send a latitude and longitude and get back, as JSON, the restrictions that apply to that point. We provide pricing, plans, and other terms individually, based on the scale and purpose of your use. Please start by contacting us through the contact form.
The API covers locations in Japan only. Text values in responses (place and facility names, notes, and the level label) are in Japanese.
What you can do
- Check a single point by latitude and longitude (GET)
- Check up to 100 points at once with a batch request (POST; each point counts as 1 use)
- Get, in one response, whether the point falls in a Densely Inhabited District (DID), airport surrounding airspace, or a Red Zone / Yellow Zone under the Small Unmanned Aircraft Flight Prohibition Act
- Checks that reflect the DID exemption for Exclusive Industrial Zones (effective July 2026)
- Detect whether a point is at sea (a point at sea that does not fall under any land-based restriction is returned as "sea")
- Get the effective height limit in airport surrounding airspace as both a value above sea level (elevation) and a value above ground level
- Check this month's usage count and your limit
- Checks use the same public data and check logic as the DroMap map
Use cases
- Automatically check whether flight is possible at the address entered in a filming or inspection request form
- Screen a list of properties or facilities for flight restrictions in one pass
- Build the check into business apps and flight planning systems
How to get started
- 1Apply through the contact formTell us your company name, purpose of use, and expected number of requests.
- 2We send you the termsWe explain the terms based on the scale and purpose of your use.
- 3Get your API key and startYou can start using the API right away with the issued API key.
Base URL
https://www.dromap.jp/api/v1
Authentication
Include your issued API key in every request, using either of the following methods.
- Request header
X-API-Key: <API key> - Or
Authorization: Bearer <API key>
Use the API key only for server-to-server communication. Do not embed it directly in browser or mobile app code. If it is embedded on the client side, third parties can read it, which may lead to unauthorized use and to your usage limit being used up.
Endpoints
GET /judge — Check a single point
| Parameter | Type | Required | Description |
|---|---|---|---|
| lat | number | Yes | Latitude |
| lng | number | Yes | Longitude |
curl "https://www.dromap.jp/api/v1/judge?lat=35.6812&lng=139.7671" \
-H "X-API-Key: YOUR_API_KEY"POST /judge — Batch check of up to 100 points
Send a JSON body with a points array (up to 100 items). Each point counts as 1 use.
| Field | Type | Required | Description |
|---|---|---|---|
| points | array | Yes | Array of the points to check (up to 100 items) |
| points[].id | string or number | - | An identifier of your choice. It is included in the response as-is. If omitted, it is null in the response |
| points[].lat | number | Yes | Latitude |
| points[].lng | number | Yes | Longitude |
curl -X POST "https://www.dromap.jp/api/v1/judge" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"points": [
{ "id": "A-1", "lat": 35.6812, "lng": 139.7671 },
{ "id": "A-2", "lat": 34.6937, "lng": 135.5023 }
]
}'The response has count (the number of points checked) andresults(an array of check results). Each element of results has the id you passed in the request, plus the same check result fields as GET /judge (level, did, airport, and so on).
{
"count": 2,
"results": [
{ "id": "A-1", "lat": 35.6812, "lng": 139.7671, /* the remaining fields are the same as GET */ ... },
{ "id": "A-2", "lat": 34.6937, "lng": 135.5023, ... }
]
}GET /usage — Check your usage
No parameters are needed. It returns this month's number of checks (uses so far) and your monthly limit as JSON. Calling GET /usage itself does not count toward the monthly number of checks.
curl "https://www.dromap.jp/api/v1/usage" \
-H "X-API-Key: YOUR_API_KEY"{
"name": "株式会社サンプル",
"plan": "",
"month": "2026-09",
"used": 1234,
"limit": 10000,
"remaining": 8766,
"perMinute": 60,
"maxBatch": 100,
"expiresAt": null
}Response fields (check result)
This is the check result format shared by GET /judge and POST /judge. Text values in responses (place names, facility names, the level label, and so on) are returned in Japanese.
| Field | Description |
|---|---|
| level / levelLabel | Overall result: prohibited (no-fly) / permission_required (permission / check required) / caution (caution) / sea (at sea) / none(no match), together with its Japanese display name (levelLabel; for example "許可・確認が必要" for permission_required). sea is a point at sea that does not fall under the land-based restriction data, and it does not mean "no restrictions" (rules such as the Port Regulations Act and the Maritime Traffic Safety Act may apply, and you may need to take care around vessels and fisheries). |
| did | Whether the point is in a Densely Inhabited District (DID) (hit) and the district name (name). If the point overlaps an Exclusive Industrial Zone and DID flight permission is therefore not required, exempt is true, and DID is not included in the overall result (level). |
| industrialZone | Whether the point is in an Exclusive Industrial Zone (hit) and the municipality name (city). These are areas excluded from "areas where people or houses are densely concentrated" by MLIT (Ministry of Land, Infrastructure, Transport and Tourism) Notice No. 435, effective July 1, 2026. The check is based on National Land Numerical Information (urban planning decision data, FY2024). In some municipalities where the data is not available, hit is false and the DID exemption is not applied (erring on the side of caution). If the data cannot be obtained, the value is null. |
| airport | Whether the point is in airport surrounding airspace (hit), the effective height limit as values for above sea level (heightLimitAmsl), above ground level (heightLimitAgl), and ground elevation (groundElevation), and the list of matching zones (zones). If heightLimitAgl is 0 or less, permission is required to fly even right above the ground. |
| airport.zones[] | Details for each matching zone: name / airport (airport name) / surface (name of the restriction surface) / limitAmsl / limitAgl / note. Zones that are not restriction surfaces (such as the airport premises) are included, so in that case airport, surface, limitAmsl, and limitAgl may be null. If the point is within the airport premises, surface is "敷地" (premises), and permission is required regardless of height. |
| redZone / yellowZone | Whether the point is in a Red Zone (the grounds of a covered facility) or a Yellow Zone (roughly 1,000 m around the facility, 2026 amendment) under the Small Unmanned Aircraft Flight Prohibition Act (hit), and the list of covered facility names (names). If the areas of several facilities overlap, the names of all matching facilities are included. |
| marine.isSea | Whether the point is at sea (a point with no GSI (Geospatial Information Authority of Japan) elevation data is treated as at sea). The value is null if it cannot be determined. Points inside a Densely Inhabited District (DID) are treated as land. |
| marine.portArea / route / trainingArea | Information on port areas and routes under the Port Regulations Act and on exercise / training areas (data from Umishiru / Japan Coast Guard). This is still in preparation, so these fields currently return null. |
| judgedAt | Date and time of the check (ISO 8601, Japan time). |
Sample response
An example of checking a point near Tokyo Station (lat=35.6812, lng=139.7671) with GET /judge. (Values may change as the actual data is updated.)
{
"lat": 35.6812,
"lng": 139.7671,
"level": "permission_required",
"levelLabel": "許可・確認が必要",
"did": { "hit": true, "name": "千代田区", "exempt": false },
"industrialZone": { "hit": false, "city": null },
"airport": {
"hit": true,
"heightLimitAmsl": 256.9,
"heightLimitAgl": 253.3,
"groundElevation": 3.6,
"zones": [
{
"name": "東京国際空港円錐表面",
"airport": "東京国際空港",
"surface": "円錐表面",
"limitAmsl": 256.9,
"limitAgl": 253.3,
"note": null
}
]
},
"redZone": { "hit": false, "names": [] },
"yellowZone": { "hit": true, "names": ["皇居"] },
"marine": {
"isSea": false,
"portArea": null,
"route": null,
"trainingArea": null
},
"judgedAt": "2026-09-28T15:29:05+09:00"
}The response is shown as returned, so text values are in Japanese. The Japanese values in this sample mean:
| Value | Meaning |
|---|---|
| 許可・確認が必要 (levelLabel) | Permission / check required (the label for permission_required) |
| 千代田区 (did.name) | Chiyoda Ward |
| 東京国際空港円錐表面 (zones[].name) | Tokyo International Airport (Haneda) conical surface |
| 東京国際空港 (zones[].airport) | Tokyo International Airport (Haneda) |
| 円錐表面 (zones[].surface) | conical surface (a type of restriction surface) |
| 皇居 (yellowZone.names) | Imperial Palace (a covered facility) |
| 株式会社サンプル (usage name) | a sample company name (Sample Co., Ltd.) |
Errors
On an error, the API returns JSON in the form {"error":{"code":"...","message":"..."}}.
| code | HTTP status | Description |
|---|---|---|
| missing_api_key | 401 | No API key was provided |
| invalid_api_key | 401 | The API key is invalid |
| key_disabled | 403 | The API key has been disabled |
| key_expired | 403 | The API key has expired |
| https_required | 403 | The request was not made over HTTPS (use https://www.dromap.jp/api/v1/) |
| invalid_parameter | 400 | A parameter is invalid |
| too_many_points | 400 | The number of points in a batch check exceeds the limit (100) |
| payload_too_large | 413 | The request body exceeds 64 KB |
| method_not_allowed | 405 | The HTTP method is not supported |
| not_found | 404 | The endpoint does not exist, or the call was made to a URL other than www.dromap.jp |
| rate_limited | 429 | The limit on requests per minute was exceeded (with a Retry-After header) |
| quota_exceeded | 429 | This month's limit on the number of checks was exceeded (with a Retry-After header) |
| internal_error | 500 | An internal server error. It is not counted toward your usage |
Usage limits
There are limits on both the number of requests per minute and the number of checks per month (set according to your contract). You can check the remaining amounts with the response headersX-RateLimit-RemainingandX-Quota-Remainingrespectively.
Notes on use
Check results are reference information created by processing public data, including DIDs from the national census (Statistics Bureau, Ministry of Internal Affairs and Communications), National Land Numerical Information (urban planning decision data and zoning) (MLIT), GSI (Geospatial Information Authority of Japan), DIPS, and covered facility information under the Small Unmanned Aircraft Flight Prohibition Act. They do not guarantee whether legal permission or approval is required. The following are not covered by the check: municipal bylaws, emergency response airspace, rules set by land and facility managers, altitudes of 150 m or more above the ground or water surface, harbor areas (Port and Harbor Act), and maritime restrictions (Port Regulations Act, Maritime Traffic Safety Act, and so on; in preparation). The DID exemption for Exclusive Industrial Zones is reflected for municipalities that have data in National Land Numerical Information (urban planning decision data). Before an actual flight, always make a final check on DIPS or a similar official source.
We provide pricing, plans, and other terms individually, based on the scale and purpose of your use. Please start by contacting us through the contact form.