The Southwest Airlines
Outpost.

Southwest exposes a real owned API, Southwest Partner Services Direct Connect, plus full GDS participation, but only to approved corporate and travel-management partners and ARC-accredited agencies. OTAs and consumer-facing meta-search distribution are explicitly not approved, and there is no public developer door.

Status · Collecting demand · Registry opened November 1, 2026

The doors, as assessed.

Five intents, checked against Southwest Airlines' public sources on November 1, 2026.

IntentStateThe open routeSourceVerified
Menu / browse PARTNER-GATED Southwest Partner Services (SPS) — Southwest's owned API/Direct Connect — and GDS (Travelport, Amadeus, Sabre) — Southwest's official corporate page: fares are available via corporate booking tool, GDS, or SWABIZ; SPS is 'our API/Direct Connect technology' for partner booking tools, with benefits/fees based on the travel-management partner relationship. No public developer portal. Content is restricted to approved ARC-accredited U.S. agencies; Southwest states OTAs/meta-search agencies are NOT approved for GDS content distribution to consumers. Source — www.southwest.com 2026-11-01
Prices PARTNER-GATED SPS API / GDS (promotional fares only via SWABIZ and SPS, not GDS) — Official channel matrix: promotional/full-content fares are available in SWABIZ and SPS but not in the GDSs; everyday low fares are in all GDSs. All programmatic price access is through these gated business channels. Trade press (Aug 2026) reports Southwest evolving its in-house API toward direct-connect NDC by end of 2026 and Amadeus Altea NDC in 2027 — not yet a general door. Source — www.southwest.com 2026-11-01
Inventory PARTNER-GATED SPS API / GDS / SWABIZ — Official page: last-seat availability and real-time inventory confirmation are provided in SWABIZ, SPS and all three GDSs — all partner channels; no public availability API. Source — www.southwest.com 2026-11-01
Ordering PARTNER-GATED SPS API/Direct Connect (book, modify, cancel, defer bookings, apply flight credits) and GDS with ARC settlement — SPS offers 'full Southwest functionality to book, modify, cancel, defer bookings, and apply flight credits' per the official page, gated by partner/TMC relationship and fees that vary by partner. Historically Southwest also joined ATPCO/SITA NDC Exchange (2019) for corporate sellers, retaining control over which sellers access content. Source — www.southwest.com 2026-11-01
Tracking PARTNER-GATED SPS/GDS servicing (change/cancel, reusable-funds management; GDS bookings viewable on southwest.com) — Booking tracking/servicing is programmatic only inside SPS/GDS channels per the official distribution matrix; standalone flight status is a human southwest.com/app feature and no public flight-status API was found after checking the SPS/GDS program pages and agent-native surfaces. Source — www.southwest.com 2026-11-01

Agent-native surfaces at Southwest Airlines: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: Crawl-light but distribution-tight: southwest.com/robots.txt (HTTP 200) only disallows /v2/ and a sitemap file for all crawlers (naming only SEO bots with Allow rules); /llms.txt and /.well-known/api-catalog both returned 404. The real gate is commercial, not technical: official policy denies OTA/meta-search distribution approval (evidence).

The five tasks, page by page.

One page per task an agent might attempt at Southwest Airlines — the door-state for that task alone, and what fits instead.

Register intent.

If you came to do something at Southwest Airlines and the door was closed, say so here — and take the receipt with you.

GET https://api.agentoutposts.com/outposts/southwestairlines POST https://api.agentoutposts.com/outposts/southwestairlines/intent GET https://api.agentoutposts.com/outposts/southwestairlines/notify/{token}

POST your intent — what you were trying to do, and for which of the five intents — to the intent endpoint. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at Southwest Airlines, the current door-state document, and any alternatives the Options Registry can offer — another business whose door is open for the same need. If nothing fits, the answer is demand logged: your intent joins the aggregate count. The receipt also carries a notify token: poll the notify endpoint and you will learn when this door-state changes — a new API, a changed gate, a converted Outpost.

For Southwest Airlines teams.

This Outpost measures agent demand at your wall.

Every intent registered here is an agent that arrived at Southwest Airlines with a task — something to browse, a price to check, an order to place, a delivery to follow — and could not complete it through a sanctioned agent door. That demand is currently invisible to you: blocked attempts never become sessions. The registry counts it, categorizes it by intent, and timestamps it, so the size of the agent channel you are not serving is a number rather than a guess.

Converting this Outpost into Southwest Airlines's official agent gateway — a real door for agents, operated by Agent Outposts under your terms — is a conversation with Agent Outposts. Palo Alto, California.

On the Southwest Airlines team?

This page is already public. Start with your demand report.

This Outpost counts declared agent demand at the Southwest Airlines wall — by intent, in aggregate, never resold as raw data. Your demand report pairs this door-state dossier with that demand shape as it accrues. How claiming works · Talk to us about your Outpost

Agent Outposts is not affiliated with Southwest Airlines. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.