DroneDeploy

DroneDeploy Annotations and Issues API

Create, read, and update annotations and Issues (field markups tied to a plan's map - points, lines, polygons, and their notes/attachments) through the schema's Issue type and its Create/Update input types (e.g. UpdateIssueInput). Modeled from the reference schema; field-level shapes are gated behind the Enterprise console.

GitHub

Documentation

📖
Documentation
https://developer-docs.dronedeploy.com/api/introduction
📖
APIReference
https://developer.dronedeploy.com/reference/updateissueinput.doc.html

Other Resources

🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/dronedeploy/refs/heads/main/graphql/dronedeploy-graphql.md
🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/dronedeploy/refs/heads/main/graphql/dronedeploy-schema.graphql
🔗
PostmanCollection
https://raw.githubusercontent.com/api-evangelist/dronedeploy/refs/heads/main/collections/dronedeploy.postman_collection.json
🔗
OpenCollection
https://raw.githubusercontent.com/api-evangelist/dronedeploy/refs/heads/main/collections/dronedeploy.opencollection.json

API entry from apis.yml

apis.yml Raw ↑ 
aid: dronedeploy:dronedeploy-annotations-and-issues-api
name: DroneDeploy Annotations and Issues API
tags:
- Annotations
- Issues
- Markups
- GraphQL
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://developer-docs.dronedeploy.com/api/introduction
baseURL: https://www.dronedeploy.com/graphql
properties:
- url: https://developer-docs.dronedeploy.com/api/introduction
  type: Documentation
- url: https://developer.dronedeploy.com/reference/updateissueinput.doc.html
  type: APIReference
- url: graphql/dronedeploy-graphql.md
  type: GraphQL
- url: graphql/dronedeploy-schema.graphql
  type: GraphQL
- url: collections/dronedeploy.postman_collection.json
  type: PostmanCollection
- url: collections/dronedeploy.opencollection.json
  type: OpenCollection
description: Create, read, and update annotations and Issues (field markups tied to a plan's map - points,
  lines, polygons, and their notes/attachments) through the schema's Issue type and its Create/Update
  input types (e.g. UpdateIssueInput). Modeled from the reference schema; field-level shapes are gated
  behind the Enterprise console.