- Getting Started
- API Home
- API Postbacks
- API Response Errors
- API Technical Details
- Client API Libraries
- HTTP Response Codes
- Email & User Profiles
- blast
- blast_repeat
- list
- send
- template
- user
- Reporting
- job
- stats
- Horizon
- content
- purchase
- Advanced & Beta Features
- ad/plan
- alert
- preview
- settings
- trigger
API
The Sailthru API allows you to efficiently take advantage of all the features Sailthru offers.
- Step 1 - Download one of our pre-built libraries for your chosen programming language. Review the list at client libraries.
- Step 2 - Install and configure your chosen pre-built library. See Set Up Config File.
- Step 3 - Write code inside your application to directly perform the desired Sailthru action.
With automation in place, less time is spent in the Sailthru interface and the experience you provide your users will be even more seamless.
Usage examples - what do customers do with the API?
The Sailthru API is a simple REST-based service. Here are some typical uses:
Send email messages to individuals
- Send a single email to an individual. Examples include a welcome email or purchase confirmation, or other transactional emails.
- API Details: "Template" call / "Send" call
Send email campaigns
Add and update user subscriptions
- Subscribe and unsubscribe email address to your Primary or Secondary lists
- See Integrate Mailing Lists via API
- API Details: "Email" call and "User" call
Perform background processing tasks
-
Start a Job, or get the status of a background Job. Examples include:
- subscriber list imports
- bulk updates of subscriber information
- exports of subscriber information
- get the status of an in-progress job
- API Details: "Job" call
Terminology and API Calls
The API has several calls across different areas. Here is a quick explanation of the various features.
Each item corresponds to a separate API call type. Please refer to the specifics of each client implementation for the exact method/function names needed to use each call.
Email delivery and subscription management
- blast - to schedule or check the status of a Campaign or 'mass mail blast' (Campaigns Overview)
- email - to access and update the subscription status of an individual email address
- list - create lists or update the subscription status of entire lists of users (Lists Overview / Integrate Lists / Setting Variables)
- send - to send, check status or delete triggered transactional email (Transactional Overview)
- template - create or edit templates for your triggered mail (Template Overview / Optimize Templates)
- user - add/change/merge identifying keys to user profiles and query by engagement
Reporting
Horizon - for hyper-personalization of email and website experiences
- content - add or update content to Horizon, triggering any matching alerts for users (see below) (Horizon in Templates)
- purchase - various aspects of ecommerce from recording an ecommerce shopping cart or checkout event to tracking abandoned shopping carts
Advanced and beta API functionalities
- ad/plan - update or get information on an AdFlight plan
- alert - update or retrieve a user's alert settings. Alerts are special transactional emails that notify subscribers of content on your site that matches their custom criteria (Alerts Overview)
- preview - preview blasts and templates
- Postbacks - Get exception/error alerts and update the information on your servers in response to user actions like opt-outs and hardbounces
- settings - display and change your settings
- trigger - create / update / delete transactional trigger (Trigger Overview)
Testing / interacting with the API directly
You can also test API calls directly in the Sailthru interface using the API Test form. Note that you must be logged in to use this feature.
Other API Topics
- API Response Errors - a complete list of the error codes you can receive from the API
- API Technical Details - If you are interested in writing your own client, or coding directly to the API
- HTTP Response Codes - list of error codes
Learning the Sailthru API
- We offer a test module called API Test in the user interface to try out API calls. Read more here.