Access to the Users API requires a valid API key or OAuth token with the socialplanner/tag.readonly scope. Keep credentials secure and rotate them regularly.
Basin authenticates using the provided API credentials and the assigned scopes. Treat Basin credentials like any other secure secret.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics
Triggered when a locationId is updated to pull the latest tag data.
Actions: Retrieve tags and sync to Basin for tagging and analytics workflows.
GET /social-media-posting/:locationId/tags
locationId, tags
Triggered when details for a tag are needed for deeper insights.
Actions: submit tagId and details payload to the API and store results in Basin.
POST /social-media-posting/:locationId/tags/details
locationId, tagId, details
Triggered to push daily or custom timeframe statistics to Basin dashboards.
Actions: post statistics payload and update analytics visuals in Basin.
POST /social-media-posting/statistics
locationId, metrics, dateRange
Set up integrations in minutes without writing code, thanks to straightforward endpoints and webhooks.
Automate data flows from the Users API into Basin dashboards and alerts.
Create scalable workflows that combine tags, details, and statistics for actionable insights.
Key elements include endpoints, authentication, and data mappings. Processes cover requesting data, handling responses, and syncing to Basin.
An API endpoint is a specific URL path that performs an action or returns data when called.
Authentication verifies identity to grant access to API resources, typically via keys or tokens.
A tag is a label used to categorize content for filtering and analytics.
Location ID identifies a specific social location or account within the API.
Automatically tag content and trigger Basin workflows based on tag changes.
Pull live statistics into Basin dashboards for real-time insights.
Wire endpoints with no code using Basin automation builders.
Create API keys, set scopes, and authorize Basin.
Turn on the endpoints you plan to use.
Run tests and monitor data flow after deployment.
Authentication uses tokens or API keys, with the socialplanner/tag.readonly scope. Ensure you have the correct scope and keep credentials secure. Rotate keys regularly and avoid embedding secrets in client-side code.
Available endpoints include: GET tags, POST tags/details, and the statistics endpoints. Not all endpoints are required for every flow; choose the ones relevant to your Basin use case.
Rate limits depend on your plan; consider caching responses where possible. If you exceed limits, implement backoff retries and stagger requests to avoid throttling.
Map fields by aligning Basin data structures with API payloads; use locationId as the primary key for linking records. Validate mappings with test calls before going live.
Yes. Use sandbox or test endpoints to simulate data flows. Review payload examples in the docs and UI previews to ensure correct shape.
Common errors usually relate to authentication failures or incorrect payload formats. Check status codes, verify credentials, and review logs for details.
Payload samples are available in the API docs and within UI templates. If you can’t find them, contact support for templates and guides.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
