API changelog

2017-09-15

  • New Position API constraints:
    • All sent payloads must now be JSON Web Tokens.
    • All devices must have a RSA 1024 bits private/public key.
    • Devices’ public key must be registered prior to sending any payload.
  • Registration API has changed:
    • registration must be sent on devices’ registration.
    • devices’ registration is made through PUT requests (vs. POST).
    • id is not anymore returned, use registration as primary key.

This is quite a huge change, please contact us if you have any trouble migrating your existing code.

2017-08-30

  • Added new endpoint /account/device/ allowing to know if a device exists on the registry. This allows to filter out positions not sent by a registered device (see next point). Example:

    http HEAD https://drone.api.gouv.fr/account/device/1234567

  • Positions API now filter out positions sent by an unregistered device (so such positions will not appear on the demo map anymore). To see unregistered positions on the /data/positions endpoint, you must explicitly request it, for example:

    https://drone.api.gouv.fr/data/positions/?north=50&south=10&west=0&east=8&registered=false

2017-08-25

  • Added login endpoint (using FranceConnect as provider):

    https://drone.api.gouv.fr/account/login?next=xxx

2017-08-11

2017-08-10

2017-07-19

This is consumed by the positions API, and also visible on the demo map: marker color will reflect the position conformity. The map also displays the areas with special UAV flight status.

2017-07-18

  • Added /data/tracks/ endpoint, to get positions grouped by track.

    https://drone.api.gouv.fr/data/tracks/

  • Added support for bbox params (north, east…) and interval for positions and tracks endpoints:

    https://drone.api.gouv.fr/data/positions/?west=-1.688964843750002&south=41.44272637767212&east=12.281250000000004&north=49.11608453987679

2017-07-05