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. Create a booking intent only after I choose, then send me the FlightSweeper approval link.
Setup flow
Every client uses the same Streamable HTTP endpoint and the same nine public tools. Booking intents return canonical state; 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 exactly nine tools and does not list create_checkout_link, book_flight, payment, or ticketing tools.
Start with search, comparison, quote details, refresh, preferences, and status before creating a booking intent.
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.