---
title: "Get Markers (Beta)"
method: GET
path: "/v0/markers"
tags: ["Markers"]
---

# Get Markers (Beta)

`GET /v0/markers`

Search markers by various parameters.

## Query parameters

- `event_time_before` string, date-time — Search for Markers before this timestamp. The timestamp should follow the ISO 8601 standard format.
- `event_time_since` string, date-time — Search for Markers since this timestamp. The timestamp should follow the ISO 8601 standard format.
- `per_page` integer — Number of results to return per page
- `page_number` integer — Return a specific page number from results

## Response `200`

List of Markers returned from GET /markers endpoint

- object
  - `data` object, required — List of Markers returned from GET /markers endpoint
    - `markers` object[], required
      - `area` string — The area that the marker is associated with. Ex. "5" (precinct number), "Downtown" (sector name), etc.
      - `description` string — Detailed description of the marker that will appear in the marker details.
      - `event_time` string, date-time — The time of the event that the marker is associated with.
      - `latitude` number — Latitude in degrees.
      - `longitude` number — Longitude in degrees.
      - `marker_details` union — Additional details about the marker. Fields contained within depend on the type of marker.
        - object
          - `caller_phone_number` string, phone-number — Phone number of the 911 caller in E.164 format (e.g., +12125551234)
          - `incident_id` string — The identifier of the incident in another system with which to associate this marker. Ex. CFS ID, etc. A pilot can enter this value manually in the UI.
          - `insights` string — AI-generated summary of the call
          - `ng911_id` string — The identifier of the NG911 call or incident. Used to identify this call in the partner application.
        - object
          - `code` string — The incident type code.
          - `incident_id` string — The identifier of the incident. Ex. case number, incident number, etc.
          - `priority` string — The priority of the incident. Ex. P0, P1, P2
        - object
          - `gunshot_detection_id` string — The identifier of the gunshot detection incident. Used to identify this incident in the partner application.
          - `incident_id` string — The identifier of the incident in another system with which to associate this marker. Ex. CFS ID, etc. A pilot can enter this value manually in the UI.
        - object
          - `drone_altitude` number — Altitude of the detected drone in meters.
          - `drone_id` string — The detected drone's serial number or other identifier.
          - `drone_manufacturer` string — The manufacturer of the detected drone. Ex. "DJI", "Parrot".
          - `drone_model` string — The model of the detected drone. Ex. "Mavic Pro", "Inspire".
          - `drone_speed` number — Speed of the detected drone in meters per second.
          - `drone_yaw` number — Yaw of the detected drone in degrees.
          - `initial_detection_latitude` number — Latitude of the detected drone's initial detection point in degrees.
          - `initial_detection_longitude` number — Longitude of the detected drone's initial detection point in degrees.
          - `pilot_latitude` number — Latitude of the pilot in degrees. 0 when the pilot location is not detected or available.
          - `pilot_longitude` number — Longitude of the pilot in degrees. 0 when the pilot location is not detected or available.
          - `protocol` string — The protocol used for RF detection.
      - `source_name` string — Partner application name. Ex. Axon, Fusus, etc.
      - `title` string — A short title for the marker that will appear on the list view for the marker.
      - `type` 'INCIDENT' | 'NG911' | 'GUNSHOT_DETECTION' | 'UAS_DETECTION' — The type of the marker. This will affect how the marker is displayed on the map view.
      - `uuid` string, uuid
      - `version` number — An increasing number that represents the version of the marker. Once this field is set, future updates must use a higher version number for changes to take effect. Updates with the same or a lower version will be ignored.
    - `pagination` object, required
      - `current_page` integer, required — Current page number of results
      - `max_per_page` integer, required — Maximum number of entries per page, could be less for final page
      - `total_pages` integer, required — Total pages of results
  - `error_message` string
  - `meta` object, required
    - `time` number
  - `skydio_error_code` integer, required
  - `status_code` integer, required

---

[API](https://skmtc.net/skydio/apis/skydio-cloud-api.md) · [All operations](https://skmtc.net/skydio/apis/skydio-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/skydio/skydio-cloud-api/revisions/0f746b116483/schema)