Jump to Content
AlacrityGuidesAPI ReferenceDiscussions
HomeGuidesAPI ReferenceChangelogDiscussions
v2.2

GuidesAPI ReferenceDiscussionsLog InAlacrity
Guides
Log In
v2.2
Delete Subscription (Unsubscribe)

Documentation

  • Introduction
    • Integrating a new service
    • Mobile Operators
    • User Journey Requirements
    • API Standards
    • Partner Responsibilities
  • The Alacrity Portal - getting started
  • Exempting MSISDNs
  • The Sandbox Environment
  • Supported Business Flows
    • One Off Charge
    • Checkout (including Two Click)
    • Pin Flow (OTP)
    • Pin Flow with Header Enrichment
    • MO SMS
    • Refund
    • Two Click
    • MO SMS Requiring Reply
    • MO SMS Routing
  • Subscription API Usage
    • Subscription Renewal
    • Subscription Status
  • Send SMS
  • Delete Subscription (Unsubscribe)
  • Eligibility Check
  • Check Transaction
  • HTTP Notifications
  • Transaction Status
  • Errors

Checkout

  • Checkout
  • Hosted Button Integration
  • Empello FraudStop - Traffic Insight

Operator Variations

  • 9mobile Nigeria
  • Axiata
  • Etisalat UAE
  • Mobily KSA
  • Ooredoo Kuwait
  • STC Kuwait
  • Telenor (all)
  • UK
  • U Mobile Malaysia
  • Unitel Mongolia
  • Zain Iraq
  • Zain Kuwait
  • Zain KSA SDP
  • Zain KW SDP

Fraud Prevention

  • Fraud Prevention
Powered by 

Delete Subscription (Unsubscribe)

Suggest Edits

Users can be unsubscribed by

  • the Delete API called by your service or
  • the user sending an SMS message or
  • customer care making a system deletion

In all cases (including the Delete API call) you will receive a HTTP notification confirming that an unsubscribe has occurred.

The Delete API call always returns success but this just confirms that the API call has been received. The HTTP notification confirms that the deletion has occurred.

Updated over 4 years ago