Reference · built on requestCommons signalEarth, seismic & volcanic

AFAD Earthquake Catalog

Earthquakes located by AFAD across Türkiye, filtered by time, area, depth, and magnitude through the apiv2 event service.

Request accessPricing ↗

About

AFAD, the Disaster and Emergency Management Presidency of Türkiye, publishes the country's earthquake catalogue on deprem.afad.gov.tr. The Event Web Service at /apiv2/event/filter returns located events filtered by start and end time, a latitude and longitude box or a radius around a point, depth, magnitude and magnitude type, with limit, offset, and orderby controls. Each record carries the eventID, location text, latitude, longitude, depth, magnitude type, magnitude, province, district, and an isEventUpdate flag. Companion pages list the latest earthquakes, focal mechanism solutions, and an instrumental catalogue from 1900 with M4.0 and above.

Through Fibric, an operator polls the box around your sites, waits for updates to settle, and proposes a lone-worker check-in, an inbound delay flag, or an incident draft for your approval.

This is a reference listing. It documents what Fibric would read from AFAD Earthquake Catalog and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Events from /apiv2/event/filter with start and end, which are required for every filter
  • Box search with minlat, maxlat, minlon, and maxlon, or radial search with lat, lon, maxrad, and minrad
  • Depth in km with mindepth and maxdepth; magnitude with minmag, maxmag, and magtype such as ML, Mw, mb, md, Ms, Mwp
  • One event by eventid, which disables every other parameter
  • Records with eventID, location, latitude, longitude, depth, type, magnitude, country, province, district, neighborhood, date, isEventUpdate, and lastUpdateDate
  • Output as XML, CSV, KML, GEOJSON, or JSON via the format parameter, ordered by time, timedesc, magnitude, or magnitudedesc
  • Focal mechanism solutions with strike, dip, and rake for both nodal planes on the event-focal-mechanism page

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Check in on lone workers after a felt quake

    When an event above your threshold lands inside the radius of a site, the operator proposes a check-in message to staff working alone there and records who answered.

    With Lone Worker

  • Flag inbound shipments from a shaken province

    The operator matches the province and district on each event to your supplier sites and proposes a delay flag on open inbound orders from them.

    With Inbound Delay

  • Open an incident with the event attached

    The operator drafts the incident with eventID, magnitude, type, depth, and location text, then updates the draft when isEventUpdate turns true.

    With Incident Draft

Requirements

  • start and end times in YYYY-MM-DDThh:mm:ss or YYYY-MM-DD form; time parameters are required for all filters
  • Either a full box or a full radial set; a radial search missing any parameter other than minrad throws an exception
  • A rule for isEventUpdate and lastUpdateDate, since AFAD revises events after first publication
  • Reference to AFAD under the Turkish Earthquake Data Center System Regulation for any data, maps, or information you reuse
Authentication
No key or account. The event filter answers plain GET requests over HTTPS.

Limits

  • Box and radial searches are incompatible; one request uses one or the other
  • The grammar labels maxrad and minrad in degrees while the example uses 100000 and 50000; test your radius first
  • The default limit is unlimited, so a wide time window without limit returns the whole span
  • No push feed or webhook; you poll the filter and compare lastUpdateDate

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request AFAD Earthquake Catalog ↗

Questions and answers

Which parameters are required on the AFAD event filter?
start and end. AFAD states that time parameters are required for all filters. Dates take YYYY-MM-DDThh:mm:ss with optional fractional seconds, or YYYY-MM-DD, where a time of 00:00:00 is assumed.
How do you search around a point instead of a box?
Give lat, lon, maxrad, and minrad. If minrad is empty the filter acts circular; if any other radial parameter is empty the API throws an exception. Radial and box search cannot be combined in one request.
What formats does the service return?
XML, CSV, KML, GEOJSON, and JSON through the format parameter. Results can be ordered by time, timedesc, magnitude, or magnitudedesc, and paged with limit and offset; values below 0 disable them. With eventid, other parameters are disabled.
Ask about AFAD Earthquake Catalog

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by AFAD, Disaster and Emergency Management Presidency of Türkiye (deprem.afad.gov.tr). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy