Get the app

Hytch Ride

Operational SMS partner integration requirements

Last updated: August 13, 2026

The Hytch Partner Portal currently provides documentation and credentials. It is not a booking UI and does not provide an SMS consent control. Each participating partner must implement the required optional unchecked control in its external booking system before operational SMS may be enabled for that integration.

Hytch Ride Operational Ride Updates: When enabled for an approved partner integration, Hytch Ride may send transactional updates for B2B or organization-arranged ride bookings, limited to confirmations, schedule, pickup, vehicle, driver, and cancellation changes.

How participating partners must collect consent

  1. Step 1: The partner booking system must identify the named traveler and the mobile number the traveler controls.
  2. Step 2: The partner booking system must show the exact disclosure below beside a separate optional control that is unchecked by default.
  3. Step 3: Only after the traveler affirmatively selects the control may the partner booking system submit the phone number and operational SMS consent record to Hytch.

Control state: optional-unchecked. The named traveler who controls the submitted mobile number must make the selection.

Disclosure participating partners must show

Yes, send me Hytch Ride SMS updates about this ride booking, including confirmation and schedule, pickup, vehicle, driver, or cancellation changes. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is not a condition of purchase. View Terms of Service and Privacy Policy.

Review the direct Terms of Service and Privacy Policy.

API contract participating partners must submit

Submit the mobile number in rider.phone and the consent record in rider.operational_sms_consent. The consent record must include:

  • consented: true
  • captured_at: ISO-8601 timestamp
  • disclosure_version: hytch-operational-sms-v1
  • evidence_reference: Unique booking-scoped consent evidence reference

Representative nested request payload:

{
  "rider": {
    "phone": "+12025550123",
    "operational_sms_consent": {
      "consented": true,
      "captured_at": "2026-08-13T12:00:00Z",
      "disclosure_version": "hytch-operational-sms-v1",
      "evidence_reference": "booking-consent-example-123"
    }
  }
}

Required retention and delivery checks

Before an integration is enabled for operational SMS, Hytch must store the booking-scoped evidence reference and consent details with the applicable ride booking.

For every enabled integration, Hytch must check the recorded consent and suppression status again at delivery before sending an operational SMS.

Consent to operational ride updates never authorizes marketing or promotional messages.

Support

For operational SMS support, email contact@hytchride.com.