Smiles APIsmiles.com.br ↗
Search Smiles miles redemption flights via API. Get pricing across Smiles, Clube Smiles, and Smiles+Money fare types for one-way and round-trip routes.
What is the Smiles API?
The Smiles.com.br API exposes 1 endpoint — search_flights — that returns available award flight options redeemable with Smiles miles. A single call returns flight objects covering departure and arrival times, duration, stop count, cabin class, seat availability, and miles pricing across four distinct fare types: standard Smiles, Clube Smiles, Smiles+Money, and Smiles+Money Club.
curl -X GET 'https://api.parse.bot/scraper/53b04628-2b65-4375-964f-37ec2643d834/search_flights?adults=1&origin=GRU&infants=0&children=0&trip_type=1&destination=GIG&return_date=2026-08-17&departure_date=2026-08-10' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace smiles-com-br-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.smiles_flight_search_api import Smiles, Flight, TripType
smiles = Smiles()
# Search one-way flights from São Paulo to Rio de Janeiro
for flight in smiles.flightsearches.search(
origin="GRU",
destination="GIG",
departure_date="2026-07-15",
trip_type=TripType.ONE_WAY,
):
print(
flight.flight_number,
flight.departure_time,
flight.arrival_time,
flight.duration,
flight.stops,
flight.available_seats,
)
print(
flight.pricing.smiles.miles,
flight.pricing.clube_smiles.miles,
flight.pricing.smiles_money.money,
)
Search for available flights using Smiles miles. Returns flight options with pricing across multiple fare types (Smiles, Clube Smiles, Smiles+Money, Smiles+Money Club). Supports both one-way and round-trip searches. Results include departure/arrival times, duration, stops, airline, seat availability, and per-fare pricing (miles, money, tax). One-way returns only SEGMENT_1 flights; round-trip returns both SEGMENT_1 (outbound) and SEGMENT_2 (return) flights.
| Param | Type | Description |
|---|---|---|
| adults | integer | Number of adult passengers |
| originrequired | string | Origin airport 3-letter IATA code (e.g. GRU, CGH, MIA) |
| infants | integer | Number of infant passengers |
| children | integer | Number of child passengers |
| trip_type | integer | Trip type: 1 for one-way, 2 for round-trip |
| destinationrequired | string | Destination airport 3-letter IATA code (e.g. MIA, GIG, LIS) |
| return_date | string | Return date in YYYY-MM-DD format. Required when trip_type is 2 (round-trip). |
| departure_daterequired | string | Departure date in YYYY-MM-DD format |
{
"type": "object",
"fields": {
"flights": "array of flight objects with segment_type, airline, airline_code, flight_number, departure_time, origin, arrival_time, destination, duration, stops, stops_text, cabin, available_seats, and pricing object containing fare types (smiles, clube_smiles, smiles_money, smiles_money_club) each with miles, money, and tax"
},
"sample": {
"data": {
"flights": [
{
"cabin": "ECONOMIC",
"stops": 0,
"origin": "GRU",
"airline": "GOL (G3)",
"pricing": {
"smiles": {
"tax": 33.64,
"miles": 33500,
"money": 0
},
"clube_smiles": {
"tax": 33.64,
"miles": 31900,
"money": 0
},
"smiles_money": {
"tax": 33.64,
"miles": 10100,
"money": 550
},
"smiles_money_club": {
"tax": 33.64,
"miles": 9570,
"money": 521
}
},
"duration": "1h 5m",
"stops_text": "Direto",
"destination": "GIG",
"airline_code": "G3",
"arrival_time": "14:10",
"segment_type": "SEGMENT_1",
"flight_number": "G3 1376",
"departure_time": "13:05",
"available_seats": 7
}
]
},
"status": "success"
}
}About the Smiles API
What the API Returns
The search_flights endpoint accepts an origin and destination as 3-letter IATA airport codes (e.g. GRU, MIA, LIS) along with a departure_date in YYYY-MM-DD format or Unix timestamp in milliseconds. It returns an array of flight objects, each carrying segment_type, airline, flight_number, departure and arrival timestamps, total duration, number of stops, cabin class, and available_seats.
Fare Types and Passenger Configuration
Each flight result surfaces pricing across multiple fare categories — standard Smiles miles, Clube Smiles (the loyalty tier), Smiles+Money (a split miles-and-cash option), and Smiles+Money Club — so callers can directly compare the miles requirement and any cash co-pay across redemption strategies. Passenger counts are configurable per search: the adults, children, and infants parameters let you price out the exact party size.
Trip Type Support
Set trip_type to 1 for a one-way search or 2 for a round-trip. When requesting a round-trip, include return_date alongside departure_date. Both date fields accept either YYYY-MM-DD strings or Unix timestamps in milliseconds, giving flexibility for integrations that already work in epoch time.
Coverage and Scope
Results reflect routes and inventory available through the Smiles program, which includes TAM/LATAM, GOL, and partner airlines operating in Brazil and internationally. Availability and fare-type options depend on the route and travel date — not all four fare types will appear on every flight result.
The Smiles API is a managed, monitored endpoint for smiles.com.br — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when smiles.com.br changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official smiles.com.br API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Compare miles costs across Smiles, Clube Smiles, and Smiles+Money fare types for a GRU–MIA route before booking
- Monitor award seat availability on specific routes to alert users when seats open up
- Build a miles-value calculator that converts the miles requirement and cash portion into a per-mile valuation
- Aggregate round-trip redemption costs for popular Brazil–Europe routes across a date range
- Display stop count and duration data to help travelers choose direct versus connecting award flights
- Power a family travel planner that prices itineraries for mixed adult, child, and infant passenger groups
- Track cabin class availability (economy vs. business) on partner airline routes within the Smiles network
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.