Reference · built on requestConnectorMarketing, reviews & analytics

Postscript

Subscribers, keywords, custom events, and opt-in webhooks from a Postscript SMS shop tied to a Shopify store.

Request accessPricing ↗

About

Postscript is an SMS marketing platform for Shopify merchants. A shop holds subscribers with promotional and transactional consent, the keywords they joined through, tags and properties, flows, and campaigns. The API at api.postscript.io is authorized with a Private API Key and returns subscribers with their shopify_customer_id. Webhooks report opt-ins, opt-outs, and incoming messages.

Through Fibric, an operator reads a subscriber's status, joins it with orders, shipments, and support cases, and proposes a custom event, a property update, or an unsubscribe for your approval. Approved calls run once and leave a record of the reason and the undo path.

This is a reference listing. It documents what Fibric would read from Postscript and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Subscribers through GET /api/v2/subscribers, with phone_number, email, shopify_customer_id, tags, properties, and promotional and transactional status
  • Subscriber filters by created_at, updated_at, phone_number, email, shopify_customer_id, and subscription_type, paged by page number
  • Keywords, the opt-in sources a subscriber joined through
  • Webhook events shop.subscriber.opt_in, shop.subscriber.opt_out, and shop.incoming_message, posted as JSON with a Postscript-Signature header
  • Incoming text messages from subscribers, delivered through the shop.incoming_message webhook

Proposed actions

  • Target capability: propose a custom event through POST /api/v2/events, with external_id set, to start a flow or release a Wait for Event step
  • Target capability: propose a subscriber property update through Update Subscriber
  • Target capability: propose adding a subscriber through POST /api/v2/subscribers with the keyword and origin that record the opt-in source
  • Target capability: propose an unsubscribe through the Unsubscribe endpoint

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Text a delay before the customer asks

    The carrier feed shows no movement. The operator proposes a custom event with the order and the new estimate, and your flow sends the text. One event per order, recorded.

    With Stalled Shipment, WISMO Deflection

  • Answer an inbound text with the order status

    shop.incoming_message delivers the reply. The operator matches the phone to a subscriber and an order and proposes the answer as a draft for your team.

    With WISMO Deflection

  • Prompt a reorder at the right interval

    From order history, the operator computes who is due and proposes a property update that your segment and flow use to send the reminder.

    With Reorder Prompt

  • Reconcile opt-outs with the help desk

    When shop.subscriber.opt_out fires, the operator matches the phone to a customer in your support tool and proposes a note so agents do not text again.

    With Contact Drivers

Requirements

  • A Postscript shop and its Private API Key; subscriber records carry the shop's shopify_customer_id
  • A keyword created in Postscript for each opt-in source the operator may add subscribers through
  • Flows in Postscript that trigger on the custom events the operator sends, under the shop name prefix Postscript adds
  • Webhook subscriptions created through the Create Webhook Subscription endpoint, pointing at an HTTPS URL, plus the signing token
Authentication
A shop's Private API Key from app.postscript.io/account/api, sent as Authorization: Bearer with a key that begins sk_.

Limits

  • Webhooks are configured only through the API, not in the Postscript app
  • Failed webhook deliveries are retried every 5 minutes for up to 1 hour, then stop
  • Custom events are matched to a subscriber asynchronously by subscriber_id, then phone, then email; an event with no match is still stored
  • Subscriber listing uses page-number pagination with page_info, not cursors

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Postscript ↗

Questions and answers

Does Postscript have webhooks?
Yes. You create a webhook subscription through the API, naming the event and the callback URL. Events include shop.subscriber.opt_in, shop.subscriber.opt_out, and shop.incoming_message. Each POST carries JSON and a Postscript-Signature header to compare against the signing token from the Get Webhook Signing Token API. Retries run every 5 minutes for up to 1 hour.
What does a custom event need?
POST /api/v2/events takes a type made of letters, digits, and underscores, one of subscriber_id, phone, or email, and optional properties, occurred_at, and external_id. Postscript prefixes the event name with your shop name in the UI and returns 202 while it matches the subscriber asynchronously.
Can the API add subscribers?
Yes, through POST /api/v2/subscribers with phone_number, a keyword ID that records the opt-in source, and an origin. The docs require compliant consent language at the point of collection, so the operator proposes the add only when your form captured that consent.
Ask about Postscript

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Postscript through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy