{
"ok": true,
"slug": "turkey-earthquakes-afad-official-data",
"count": 2,
"items": [
{
"eventId": "734694",
"magnitude": 1.5,
"magnitudeType": "ML",
"date": "2026-11-20T20:57:11",
"latitude": 38.543,
"longitude": 38.00683,
"depthKm": 7,
"location": "Yazıhan (Malatya)",
"province": "Malatya",
"district": "Yazıhan",
"neighborhood": "İriağaç",
"country": "Türkiye",
"rms": 0.76,
"isEventUpdate": false,
"source": "AFAD",
"scrapedAt": "2026-11-20T22:01:44.738Z"
},
{
"eventId": "734693",
"magnitude": 1.9,
"magnitudeType": "ML",
"date": "2026-11-20T20:54:22",
"latitude": 40.03483,
"longitude": 27.41633,
"depthKm": 11.16,
"location": "Yenice (Çanakkale)",
"province": "Çanakkale",
"district": "Yenice",
"neighborhood": "Çamoba",
"country": "Türkiye",
"rms": 0.34,
"isEventUpdate": false,
"source": "AFAD",
"scrapedAt": "2026-11-20T22:01:44.849Z"
}
]
}
curl --location --request GET 'https://zylalabs.com/api/15129/turkey+earthquakes+afad+official+data+api/40366/get+live+data?query=technology&category=general&country=GLOBAL&limit=10' --header 'Authorization: Bearer YOUR_API_KEY'
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 Turkey Earthquakes AFAD Official Data API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Turkey Earthquakes - AFAD Official Data. Delivers normalized JSON results with high uptime and low latency.
Requests execute synchronously against our cloud intelligence engine and typically return structured JSON within a few seconds.
Yes. Every endpoint returns deterministic JSON schemas designed for LLMs, RAG pipelines, and scheduled B2B workflows.
It returns normalized JSON records for earthquakes detected in Türkiye by AFAD. Each item represents an event and may include its magnitude, location, coordinates, depth, timestamp, source, and event status.
Records can include eventId, magnitude, magnitudeType, date, latitude, longitude, depthKm, location, province, district, neighborhood, country, rms, isEventUpdate, source, and scrapedAt. Field availability may vary by source record.
The response is a JSON object containing an ok status, the API slug, a count of returned records, and an items array. The count indicates the number of records in items, while each array element contains one earthquake event.
The endpoint covers earthquake events reported in Türkiye, including regional details such as province, district, neighborhood, and country. For example, a record may identify Yazıhan district in Malatya province.
Magnitude is the measured earthquake size, while magnitudeType identifies the scale, such as ML. depthKm gives the event’s depth below the surface in kilometers. For example, an event may have magnitude 1.5, type ML, and depth 7 km.
Date is the earthquake event timestamp, provided in ISO-like date-time format. scrapedAt records when the API collected the source data. These fields help distinguish the event occurrence from data retrieval time.
EventId is the source event identifier and can help applications recognize or deduplicate records. isEventUpdate indicates whether the record represents an update to an existing event rather than a newly reported event.
Check the ok value and count before processing items. An empty items array means no records were returned for that response. Applications should also treat optional location or quality fields as nullable and avoid assuming every record contains identical detail.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund