Web API access blocked (403 browser_signature_banned) – integrating SmartFarm Agras data

Flight Reader
1

Hi Mike,

We’re an agricultural operator in Brazil flying DJI Agras T70P drones. We’re testing Flight Reader Web with DJI SmartFarm sync, and it works well: flights sync and process correctly.

Our goal is to bring these flights, including the AG fields (spraying state, spray used, task area, spray width), into our own farm management platform automatically, for our own operation.

I generated a key in Settings > API and made a single server-side call (Python) to GET https://app-api.flightreader.com/v1/account. It returned 403 with error_name “browser_signature_banned”. We haven’t retried, since the response said not to.

A few questions:

  1. What is the expected way to call the Web API from a server? Is there a required User-Agent or client format? And is our account or IP now flagged?
  2. Does GET /v1/flights return SmartFarm-synced flights? On Plus, does /exports/csv/{templateName} include AG.* fields from a custom template?
  3. Or should we use the Flight Reader API (api.flightreader.com) with the SmartFarm endpoints instead? Which product fits this use case better?
  4. Is this kind of integration allowed on Plus for our own operation? Would we need a separate agreement if, later on, our clients connect their own accounts?

Happy to share account details privately if that helps.

Thanks for building this!

2

To answer your questions:

  1. Cloudflare was blocking your requests. They should be unblocked now.

  2. GET /v1/flights returns any type of flight imported into Flight Reader Web. With a Plus account, you can export all available fields, including the AG.* fields.

  3. If you’re not planning to use the Flight Reader Web interface to view and work with your flight data, the Flight Reader API is probably going to be the better option. Either one could work, but the Flight Reader API would likely be simpler for what you’re trying to do.

  4. You can use the Flight Reader Web API to work with flights from drones you own. If you’re also going to be working with your customers’ flight data, each customer would need their own Flight Reader Web account where they store the flight logs from their drones.

Again, that setup probably only makes sense if your customers also plan to use Flight Reader Web. If your only need is to process flight logs and access the resulting flight data through an API, the Flight Reader API is going to be much easier to manage for that type of workflow.

Let me know if you have any other questions.