Use OAuth with your SaaS API to grant read access to installed locations and manage tokens. The required scope is oauth.readonly to begin with, ensuring safe and auditable access.
Authenticate 2Chat to access the SaaS API endpoints. This flow pairs your app with a secure token exchange and short-lived credentials for each connection.
Core endpoints include GET /oauth/installedLocations, POST /oauth/locationToken, saas/location.write, PUT /update-saas-subscription/:locationId, and POST /enable-saas/:locationId. Additional endpoints may be used as needed for location management and subscription control.
Trigger: User connects a new SaaS location and approves access for 2Chat.
Actions: fetch installedLocations, request a locationToken, and store the token securely for future calls.
GET /oauth/installedLocations followed by POST /oauth/locationToken
locationId, accessToken, refreshToken, tokenExpiry
Trigger: After token retrieval, create or update a SaaS location record.
Actions: call saas/location.write to register the location, then POST /enable-saas/:locationId to activate the integration.
POST /saas/location.write and POST /enable-saas/:locationId
locationId, SaaS plan, status, activationDate
Trigger: A subscription change is detected or user updates the plan.
Actions: update the subscription with PUT /update-saas-subscription/:locationId and verify the new status.
PUT /update-saas-subscription/:locationId
locationId, newPlan, subscriptionStatus
Drag-and-drop flow to connect APIs without writing code, speeding up onboarding and updates.
Unified management of locations and subscriptions from a single dashboard.
Secure, auditable OAuth with scoped access and token rotation built in.
Glossary of terms and processes used in the SaaS API and 2Chat integration, including endpoints, locations, tokens, and subscriptions.
OAuth is an open standard for access delegation that allows 3rd-party apps (like 2Chat) to access a user’s data without exposing credentials directly.
An API endpoint is a specific URL that performs an action, such as retrieving installed locations or updating a subscription.
A SaaS location represents an instance of the integration tied to a particular account or organization.
A subscription links a location to a plan, enabling or restricting features within the integration.
Set up a guided flow that creates a SaaS location, authorizes 2Chat, and provisions default subscriptions automatically.
Use webhooks to push location and subscription changes from SaaS API into 2Chat for real-time sync.
Track token expiries, location activity, and error rates to maintain high reliability of the integration.
In the SaaS API dashboard, create a new location and authorize 2Chat to access it using OAuth.
Exchange the authorization for a locationToken, then register the location with saas/location.write.
Enable the SaaS integration with POST /enable-saas/:locationId and verify data flow to 2Chat.
No-code or low-code options are available via the app connector and dashboard. You can configure the initial connection using the visual flow and only minimal data mapping is required. If you need advanced customization, you can extend the integration with additional endpoints as your workflow grows.
The required scope to begin is oauth.readonly. This allows reading installed locations and token management. You can request higher scope later if you need write access.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
