Overview
Overview
Developers can access out-of-the-box actions across supported services using our Actions API.
Right now, the only supported Actions API is the Messaging API (documented below). Additional Actions APIs for other verticals will be documented here in the future.
Messaging API
Overview
The first Actions API product is our Messaging API. This product enables developers to programmatically send and receive messages across popular social messaging services without handling authentication or building browser automation scripts themselves.
Supported Integrations
| Name | Reference |
|---|---|
| See Reference | |
| Coming soon… | |
| X/Twitter | Coming soon… |
| Coming soon… | |
| Coming soon… |
Features
- Handle authentication via our Link SDK product. This includes collecting and validating end-user credentials, multi-factor authentication, proxying, and more.
- Send messages using a consistent API for all messaging services without worrying about the complexity of managing multiple integrations.
- Register webhooks for real-time events, including robust reliability and automatic retries to ensure you never miss a message.
- Easily manage end-user access, including push notifications to re-authenticate users and controls to easily revoke user authentication.
Product Flow
User launches Link SDK
Window pops up prompting your end-user to install the Chrome extension.
User installs Chrome extension
Your end-user installs the Chrome extension and logs into the account with which they want your app to perform actions on.
Link SDK saves the user session
Your end-user’s session can now be accessed via the Link SDK.
Use the saved session to automate actions
Your app can now use this session via !
Anon is currently in private beta. To get access to start building on our platform, click here.
To start building, check out our Getting Started guide, or head to our API Reference to dig deeper.
Was this page helpful?