Pre-Built Tooling
| Category | Details |
|---|---|
| Authentication | Bearer Token + Shop Token (Header: X-Postscript-Shop-Token) |
| Two-Way Sync | No |
| Events Supported | No |
| Realtime | Polling |
| Supports Rate Limiting | Yes |
| Authentication Scopes Supported | N/A (Token-based) |
Objects Supported
Alloy Automation supports syncing the following objects from Postscript:- Subscribers
- SMS Campaigns
- Keywords
- Message History
- Opt-ins/Opt-outs
Set Up Guide
Trial Access
| Question | Answer |
|---|---|
| Offers free trial? | Yes. Postscript offers a free trial with limited SMS credits. Start free trial |
| Requires paid sandbox? | No. The trial account can be used for testing and development. |
| Requires partnership to obtain authentication? | No. However, you need an active Postscript account integrated with your e-commerce platform. |
Authentication (Bearer Token + Shop Token)
For customers who want to completely whitelabel their authentication experience, you can provide your own developer keys instead of using Alloy Automation’s. For detailed API documentation, visit Postscript API Reference.Use Cases
1) SMS subscriber synchronization
Sync SMS subscriber data from Postscript to your CRM or customer data platform to coordinate marketing campaigns across email, SMS, and other channels.2) Abandoned cart SMS automation
Trigger abandoned cart recovery SMS messages through Postscript when customers leave items in their cart, using data from your e-commerce platform.3) Post-purchase engagement
Automatically send post-purchase SMS messages via Postscript for order confirmations, shipping updates, review requests, and cross-sell opportunities.4) SMS campaign analytics
Pull SMS campaign metrics and subscriber engagement data from Postscript into your analytics platform to measure SMS marketing ROI.5) Keyword-based automation
Set up automated SMS workflows triggered by customer keyword responses in Postscript, integrating with other systems to fulfill requests or gather data.API Gotchas
- Dual authentication: Postscript requires both a Bearer token (Private Key) and a Shop Token in separate headers. Ensure both are configured correctly or all API requests will fail.
-
Partner key requirement: Some API operations may require a
POSTSCRIPT_PARTNER_KEYconfiguration variable. Check with Postscript if you’re a partner or need extended API access. - Subscriber consent: Always respect SMS opt-in/opt-out status when working with subscriber data. Sending messages to opted-out subscribers can result in compliance violations and account suspension.
- Rate limiting: Postscript enforces rate limits to protect system performance. Implement exponential backoff retry logic for handling rate limit responses.
- Phone number formatting: Ensure phone numbers are properly formatted (typically E.164 format) before sending them to the Postscript API to avoid validation errors.
For questions or troubleshooting, contact support@runalloy.com.