← All integrations

Ambee

29 operations0 webhooks

Environmental data API for air quality, pollen, weather, and wildfire information.

Supported operations

  • Get Forecast By Lat LngRead-only

    Get the hourly air quality forecast for a latitude/longitude (next 48 hours)

  • Get History By Lat LngRead-only

    Get hourly historical air quality for a latitude/longitude over a time range

  • Get History By Postal CodeRead-only

    Get hourly historical air quality for a postal code over a time range

  • Get Latest By CityRead-only

    Get the latest air quality for the stations in a city

  • Get Latest By Country CodeRead-only

    Get the latest air quality for the monitoring stations across a country

  • Get Latest By Lat LngRead-only

    Get the latest air quality (AQI and pollutant concentrations) for a latitude/longitude

  • Get Latest By Postal CodeRead-only

    Get the latest air quality for a postal code and country

FAQ

Install corsair and @corsair-dev/ambee, add the Ambee plugin, and connect with an API key. Then call methods like corsair.ambee.api.airQuality.getForecastByLatLng() from your app. Corsair syncs data per tenant.

Yes. Ambee requires an API key from your Ambee account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Ambee, GitHub, Notion, Stripe, and the rest. Trigger Ambee from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for environmental data api for air quality, pollen, weather, and wildfire information. Common builds include sync jobs, admin tooling, and agents that call Ambee APIs from your backend. Local DB entities let you query synced Ambee records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Ambee API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/ambee in the open repo. When Ambee ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Ambee data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Ambee data on your behalf.