aid: supercom
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/supercom.png
name: Super.com
description: 'Super.com (formerly SnapTravel and Snapcommerce) is a consumer savings company founded
  in 2016 by Hussein Fazal and Henry Shi, headquartered in San Francisco with engineering roots in
  Toronto. Its app bundles SuperTravel hotel booking, flights, SuperShop savings, SuperCash cash back
  and credit building, SuperPay, and SuperRx prescription discounts, and the company reports more than
  $2 billion in sales processed since launch on roughly $150 million raised across seed through Series C.
  Its only developer-facing surface is the SnapTravel Partner Search API at api.snaptravel.com — a hotel
  search-and-book integration offered to business partners. No public API reference, developer portal,
  or machine-readable specification is published: every documentation path on the API host returns 404,
  no developer/docs subdomain resolves, and the www.super.com HTML surface is served behind a Cloudflare
  bot challenge. The company does publish an RFC 9116 security.txt naming a security contact and an
  invite-only Bugcrowd program.'
url: https://raw.githubusercontent.com/api-evangelist/supercom/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.23'
created: '2026-08-05'
modified: '2026-08-05'
tags:
- Company
- Travel
- Hotels
- Booking
- Flights
- Consumer Finance
- Cash Back
- Savings
- Prescription Discounts
- Mobile Applications
apis:
- aid: supercom:snaptravel-partner-search-api
  name: SnapTravel Partner Search API
  description: >-
    The partner-facing hotel search API operated by Super.com under its original SnapTravel brand.
    The host is live and self-identifies ("Welcome to the Partner Search API for SnapTravel"), but the
    API is available only through a business partnership: no public reference, OpenAPI, Swagger,
    GraphQL SDL, or Postman collection is published at any Super.com or SnapTravel host.
  humanURL: https://api.snaptravel.com/
  baseURL: https://api.snaptravel.com
  tags:
  - Hotels
  - Search
  - Travel
  - Booking
  - Partners
  x-evidence:
    fetched: '2026-08-05'
    url: https://api.snaptravel.com/
    http_status: 200
    content_type: text/html; charset=utf-8
    body: Welcome to the Partner Search API for SnapTravel
    note: >-
      /openapi.json, /openapi.yaml, /swagger.json, /api-docs, /docs, /redoc, /v1/openapi.json,
      /graphql, /llms.txt and every /.well-known/* path on this host returned 404 on 2026-08-05.
  properties: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: VulnerabilityDisclosure
  url: security/supercom-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/supercom-domain-security.yml
- type: Website
  url: https://www.super.com/
- type: GitHubOrganization
  url: https://github.com/snaptravel
- type: HelpCenter
  url: https://www.super.com/help
- type: SecurityTxt
  url: well-known/supercom-security.txt
- type: WellKnown
  url: well-known/supercom-well-known.yml
- type: LLMsTxt
  url: llms/supercom-llms.txt
- type: Security
  url: security/supercom-vulnerability-disclosure.yml
x-coverage:
  state: gated
  reason: sales-gate
  detail: >-
    api.snaptravel.com answers 200 with the plain-text line "Welcome to the Partner Search API for
    SnapTravel" but every documentation path on it 404s, no developer/docs/partner subdomain resolves
    for super.com, and the hotel search API is only obtainable through a business partnership — so
    there is no public reference or machine-readable spec to harvest.
  evidence:
  - url: https://api.snaptravel.com/
    status: 200
  - url: https://api.snaptravel.com/openapi.json
    status: 404
  - url: https://api.snaptravel.com/api-docs
    status: 404
  - url: https://www.super.com/
    status: 403
  checked: '2026-08-05'
x-enrichment:
  date: '2026-08-05'
  status: minimal
  artifacts_added: 5
  pass: local-v1