Connect FlightSweeper to Poke
Use FlightSweeper from Apple Messages, Telegram, WhatsApp, and RCS through Poke while keeping identity, compliance, approval, traveler data, and payment on FlightSweeper.
OAuth setup supported
Poke connects to FlightSweeper with OAuth authorization code, PKCE, rotating refresh tokens, and an owner-scoped access token. The client never receives passenger identity or payment data.
Poke users who want conversational flight search and booking-intent handoff without giving the messaging assistant payment or ticketing authority.
Use FlightSweeper to search live flights for this trip. Show the all-in total, quote time, expiry, refund terms, and FlightSweeper's role. After I choose and ask to buy, call book_flight, send me the hosted approval link, and resume it when I finish.
Setup flow
Every client uses the same Streamable HTTP endpoint and documented public tool set. The primary book_flight action hides the internal intent and approval stages; approval and payment stay hosted.
FlightSweeper publishes OAuth discovery and Dynamic Client Registration. OAuth access tokens expire after 10 minutes, refresh tokens rotate, and the connection can be revoked from FlightSweeper.
Open the FlightSweeper integration in Poke and confirm the server URL is https://flightsweeper.com/api/agent/mcp.
Authorize Poke with FlightSweeper OAuth. FlightSweeper, not the Poke user header, binds the connection to your owner account.
Confirm Poke discovers the documented public tools, including resumable book_flight, booking reads, and advanced discovery, without exposing create_checkout_link, raw payment, or direct ticketing.
Start with search and comparison. Call book_flight only after I choose an exact quote and ask to buy.
Open every approval or checkout URL on FlightSweeper. Never send passenger identity or card data through Poke.
Tool permissions
Every client should keep the same transaction boundary: search can happen in the agent, but booking happens after the traveler confirms a hosted checkout page.