Developers
Developer documentation
Build on DroneJob through APIs and events that connect operational context to your systems. Start with the public overview to evaluate fit; registered developers use the detailed implementation documentation for their technical work.
Read the public API and event overview to assess fit. Discuss My Integration requests an email follow-up; it does not enroll you or grant developer access.
Connect a useful event to a responsible next action.
Illustrative integration: a reviewed mission change informs a downstream service workflow.
Your source system owns its record. An authorized exchange carries the agreed operational context to the receiving workflow. The receiving owner reviews exceptions, acknowledges the result and keeps the manual fallback clear. Define the trigger, minimum data, permission boundary and completion evidence before implementation.
- Evaluate: describe the workflow, source and destination systems, and the useful outcome.
- Define: agree data ownership, event meaning, access, review and failure handling.
- Implement: registered developers consult the detailed technical documentation.
- Review: responsible owners verify the exchange and acceptance evidence.