Renfe
Use Renfe data APIs through OpenAny to search train journeys, compare calendar fares and inspect stations and train calling points. For lowest fare per day, supply origin and destination in the query; optionally select departure offset in days to set the requested scope. Other available operations include stations, train calling points, train search. Use these results to compare the lowest displayed fares across dates before choosing a date for detailed travel searches. A fare-calendar request covers at most 92 days. Each API page provides supported parameters, request and response examples, and usage pricing.
- Endpoints
- 4In this collection
- Providers
- 1Unique providers
- Requests
- —Loading...
- Success rate
- —Loading...
- Response P50
- —Loading...
Available APIs
Renfe lowest fare per day API
Use the Renfe lowest fare per day API to retrieve price information and quoted price as structured JSON from Renfe. Supply origin and destination in the query; optionally select departure offset in days to set the requested scope. Use these results to compare the lowest displayed fares across dates before choosing a date for detailed travel searches. A fare-calendar request covers at most 92 days. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
Renfe train calling points API
Use the Renfe train calling points API to retrieve station and stop records, journey segments and endpoints, calculated distance and record identities and titles as structured JSON from Renfe. Supply train number in the query; optionally select date and departure offset in days to set the requested scope. Use these results to compare journey options for the selected route and dates before choosing a travel itinerary. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
Renfe stations API
Use the Renfe stations API to retrieve station records and record identities and titles as structured JSON from Renfe. Choose search words as optional query conditions to select the source records or view required for your request. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
Renfe train search API
Use the Renfe train search API to retrieve fare conditions, train records, duration information, clock-change records, quoted price and journey segments and endpoints as structured JSON from Renfe. Supply origin and destination in the query; optionally select date and departure offset in days to set the requested scope. Use these results to compare journey options for the selected route and dates before choosing a travel itinerary. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
Common questions
How are Renfe APIs priced?
Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.
How do I authenticate Renfe requests?
Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.
Are all implementations interchangeable?
No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.
Use Renfe with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.