Configure OAuth on the SaaS API so Adafruit IO can call resources securely. Start with oauth.readonly and rise to write scopes as your needs grow.
Create an OAuth client in Adafruit IO and complete the authorization flow to grant SaaS API permission to access your data.
GET /oauth/installedLocations; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId; additional endpoints are documented as you scale.
Trigger: When a new location is added in Adafruit IO, fetch installed locations in the SaaS API to initialize the integration.
Actions: call GET /oauth/installedLocations, then POST /oauth/locationToken to obtain an access token and store it for future calls.
GET /oauth/installedLocations; POST /oauth/locationToken
locationId, clientId, clientSecret, accessToken
Trigger: A location is activated in Adafruit IO and you enable SaaS for that location.
Actions: call POST /enable-saas/:locationId to enable SaaS, then PUT /update-saas-subscription/:locationId to set the subscription.
POST /enable-saas/:locationId; PUT /update-saas-subscription/:locationId
locationId, subscriptionDetails
Trigger: When data changes in Adafruit IO sensors, push updates to SaaS API.
Actions: use saas/location.write to push data; manage location tokens for authentication.
saas/location.write
locationId, dataPayload
Easily automate data flow between Adafruit IO and SaaS API without custom code using pre-built GHL connectors.
Speed up integration with OAuth, quick endpoint calls, and robust error handling.
Scale your data operations across locations with centralized subscription management.
A quick glossary and process overview to help you implement the SaaS API integration with Adafruit IO using GHL.
OAuth is an open standard for access delegation, allowing Adafruit IO to access SaaS API resources securely without sharing passwords.
An endpoint is a specific URL through which you can perform actions on SaaS API, such as retrieving installed locations or updating a subscription.
A token is a string used to authenticate API requests, often short-lived and scoped.
A subscription controls which SaaS API features are enabled for a given Adafruit IO location and user.
Automatically push Adafruit IO sensor events into SaaS API, enabling real-time monitoring and alerting.
Configure alerting workflows when readings cross thresholds, using SaaS API to activate automations.
Record who changed data and when, with SaaS API storage and analytics capabilities.
Register your SaaS API app in the GHL developer console to obtain client credentials.
Configure the OAuth flow in Adafruit IO to request access to SaaS API resources.
Test the integration end-to-end and deploy to production with monitoring.
Yes. The SaaS API (GHL) acts as the backend service, while Adafruit IO is the app that connects to it through the GHL connector. This integration uses OAuth for secure access and starts with the oauth.readonly scope before requesting additional permissions as needed. You can begin by calling the endpoints to read installed locations and then exchange a token for continuous requests.
No-code integration is possible with the GHL connectors in many cases. You can set up OAuth in Adafruit IO and map fields without writing code. The endpoints handle data transfer without custom scripts. For complex flows, lightweight scripting can be used, but the core integration is designed to be code-free for most use cases.
Endpoints like GET /oauth/installedLocations, POST /oauth/locationToken, POST /enable-saas/:locationId, PUT /update-saas-subscription/:locationId, and saas/location.write are used to manage installation, authentication, and data write operations. Documentation provides examples and field mappings for each endpoint to ensure correct usage.
OAuth is recommended and commonly required to securely access SaaS API resources. Start with oauth.readonly and request additional scopes as your integration needs evolve. The flow protects credentials and ensures tokens are scoped to your Adafruit IO account and locations.
Test the connection by simulating a new location in Adafruit IO, verifying location installations via GET /oauth/installedLocations, then exchanging a token with POST /oauth/locationToken. Validate data writes with saas/location.write and check subscription updates via PUT /update-saas-subscription/:locationId. Use test data and sandbox environments where available before going to production.
Yes. The setup scales across multiple locations by managing per-location tokens and subscriptions. Use locationId to segment data and enable SaaS per site. Centralized monitoring and error handling help maintain reliability as you expand.
Microsoft Learn, SaaS API developer docs, and the GHL connector guides provide additional resources. You can also access community forums and support channels for practical integration tips.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
