Authenticate Sakari SMS to the Users API using a single API key or OAuth token with the scope socialplanner/tag.readonly. Keep credentials secure and rotate them on a schedule.
Sakari SMS authenticates to the Users API with the credentials you provide. Apply least privilege and store keys securely in your vault.
GET /social-media-posting/:locationId/tags fetch location tags; POST /social-media-posting/:locationId/tags/details fetch tag details; socialplanner/statistics.readonly retrieve statistics; POST /social-media-posting/statistics submit statistics
Trigger when a contact is created or updated in Sakari SMS to pull associated tags from the Users API
Actions include updating contact tags and syncing campaigns across both systems
GET /social-media-posting/:locationId/tags
locationId, tags
Trigger after posting content in Sakari SMS to obtain tag details and performance metrics from the Users API
Actions include updating analytics dashboards and syncing engagement data
POST /social-media-posting/:locationId/tags/details
locationId, tagDetails, detailsId
Trigger daily to pull statistics from the Users API and feed Sakari SMS dashboards
Actions include updating KPI dashboards and sending alerts when thresholds are met
GET /socialplanner/statistics.readonly
statisticsId, locationId, metrics
Fast setup with no coding required using built in connectors
Automated data sync between Sakari SMS and the Users API reduces manual work
Clear analytics from a unified data view across platforms
Definitions of API terms, endpoints, triggers and data fields used in this no code integration
A set of rules that lets Sakari SMS talk to the Users API and exchange data
A specific URL path that performs an action when called
A URL on Sakari SMS that can receive real time event notices from the Users API
A credential used to prove identity when making API calls
Use tag changes to trigger targeted messages and updates in the Users API
Aggregate events from Sakari SMS into a live analytics view in the Users API
Create multi step automations that move data between both systems with minimal effort
Obtain API keys or OAuth tokens and grant the needed scope for tag access
Connect the endpoints to Sakari SMS fields and test the flow
Run end to end tests and then turn on the automation
Authentication uses the API key or OAuth token with the scope socialplanner/tag.readonly. Store securely and rotate. In Sakari SMS, enter the credentials in the connection setup and complete the consent flow if using OAuth. Keep access tied to the least privilege.
Tag endpoints include getting tags and details. Use GET and POST calls to fetch and enrich data, map tags to contacts, and drive campaigns.
API tokens should have only the necessary permissions. Use the socialplanner tag read only scope and restrict access per user.
No code is required thanks to the built in connectors. Set up triggers, actions and mappings visually and test with sample data.
Test the connection in a sandbox, review logs, and verify data consistency across Sakari SMS and the Users API before going live.
Yes. Use dashboards, reports and alerts to monitor data flows and be alerted to any failures or delays.
Common fields exchanged include locationId, tags, tagDetails, statistics and metrics depending on the endpoint.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
