Skip to main content
The Emergency API provides endpoints for managing emergency alerts in FreeTAKServer. Emergency alerts notify connected clients of urgent situations and can include location data.

Get Emergencies

Retrieve all active emergency alerts.

Authentication

This endpoint requires HTTP Basic Authentication.

Response

array
Array of emergency objects

Response Example

Create Emergency Alert

Create and broadcast a new emergency alert to all connected clients.

Authentication

This endpoint requires HTTP Basic Authentication.

Request Body

string
required
Type of emergency. Valid values:
  • 911 Alert - General emergency alert
  • Ring The Bell - Urgent attention required
  • Geo-fence Breached - Location boundary violation
  • In Contact - Contact with hostile forces
float
required
Latitude coordinate of the emergency location
float
required
Longitude coordinate of the emergency location
string
Callsign or name of the emergency source
string
Additional details about the emergency

Response

string
The UID of the created emergency event

Response Example

Delete Emergency Alert

Cancel an active emergency alert and notify all clients.

Authentication

This endpoint requires HTTP Basic Authentication.

Request Body

string
required
The UID of the emergency alert to cancel

Response

string
The UID of the cancelled emergency

Response Example

Emergency Types

FreeTAKServer supports the following emergency types:

Emergency Broadcasting

When an emergency is created or deleted:
  1. The event is serialized to CoT format
  2. Broadcast to all clients on TCP CoT service
  3. Broadcast to all clients on SSL CoT service
  4. Stored in emergency persistence for retrieval

Error Responses

Emergency endpoints return standard error responses for authentication failures and internal errors. If an emergency object is missing required attributes, it will be logged but not included in the response list.