Starting September 1, 2026, any new
x-api-key you create
in Airbase must be used alongside a Partner Key (x-partner-key)
that identifies the third-party software making the call.
Why we're making this change
Today, a request to the DroneSense API is authenticated only by your organization's x-api-key. That tells us who owns the data being accessed, but not what software is accessing it. As the number of integrations connecting to DroneSense has grown — Real-Time Crime/Information Center solutions like Flock and Fusus, custom Esri and TAK integrations, and homegrown scripts — we need a way to know which integrations are connecting, control what each one can do, and respond quickly if something goes wrong.
What's changing
- Effective September 1, 2026, integrations will send two headers:
x-api-key(your organization, generated by you in Airbase) andx-partner-key(the third-party software, issued by DroneSense). - API Keys created before September 1, 2026 are grandfathered and continue to work indefinitely without a Partner Key.
-
API Keys created on or after September 1, 2026 require a Partner Key. Requests missing it will be rejected with
401 Unauthorized.
Who needs to do something
| If you... | Then... |
|---|---|
| Use a vendor integration (Flock, Fusus, or similar) | Confirm with your vendor that they support the Partner Key requirement. They manage it — you don't. |
| Built your own integration (Esri, TAK, or an in-house script) | Submit a support ticket describing your integration, and we'll issue a Partner Key for your organization. |
| Have a working integration using a key created before Sept 1, 2026 | Nothing — it keeps working as-is. |
| Have the External API feature but don't currently use it | Nothing now — but keep this in mind if you set up an integration after September 1, 2026. |
Not sure which applies to you? Check Admin → Integrations → API Keys in Airbase, or submit a support ticket and we'll help you figure it out.
Where to go for more detail
For full setup instructions, authentication details, and troubleshooting, see our API Integrations article.
Comments
0 comments
Article is closed for comments.