This API delivers detailed and current information about electric vehicle (EV) charging stations and alternative fuel stations. It is designed to simplify the process of locating available stations in specific areas. The API offers extensive data, including geographic location, connector types, access hours, operational status, and more, enabling seamless integration into applications and systems that manage sustainable mobility infrastructure.
The response includes multiple layers of information, providing both aggregate data (such as the total number of stations) and specific details for each station. It specifies the latitude and longitude coordinates of the requested area, along with the country and search accuracy level, allowing for searches at the locality, city, or regional level.
In summary, the EV Charge Locator API provides access to comprehensive information on charging infrastructure and alternative fuels. Its emphasis on precise data, frequent updates, and compatibility with various connector types makes it an invaluable resource.
The Location parameter accepts addresses in several formats: street, city, state, zip code; city and state; or zip code only.
You must also specify a fuel_type:
all All Fuels
BD Biodiesel (B20 and above)
CNG Compressed Natural Gas (CNG)
ELEC Electric
E85 Ethanol (E85)
HY Hydrogen
LNG Liquefied Natural Gas (LNG)
LPG Propane (LPG)
RD Renewable Diesel (R20 and above)
The radius parameter specifies the search area in miles, allowing a range up to 500 miles or an infinite value.
The status parameter allows you to filter stations by status. You can specify a single status or a comma-separated list, including: all, E (available), P (planned), and T (temporarily unavailable).
The limit parameter determines the maximum number of results that will be returned in the API response. Default. An integer value ranging from 0 to 200 can be passed to control the number of results you wish to receive. In addition, you can use the special value “all” to retrieve all available results without restriction.
Stations Finder - Endpoint Features
Object | Description |
---|---|
location |
[Required] Indicates a location |
fuel_type |
[Required] Indicate a fuel type |
radius |
[Required] Indicates a radius (max. 500 miles) |
status |
[Required] Indicate the status of a station according to its current status |
limit |
[Required] Specifies a number of results (max 200). |
{"latitude":40.42487,"longitude":-3.68355,"location_country":"ES","precision":{"value":5,"name":"postal_code","types":["postal_code"]},"station_locator_url":"https://afdc.energy.gov/stations/","total_results":0,"station_counts":{"total":0,"fuels":{"BD":{"total":0},"E85":{"total":0},"ELEC":{"total":0},"HY":{"total":0},"LNG":{"total":0},"CNG":{"total":0},"LPG":{"total":0},"RD":{"total":0}}},"offset":0,"fuel_stations":[]}
curl --location --request GET 'https://zylalabs.com/api/5315/ev+charge+locator+api/6870/stations+finder?location=00 Sesame Rd, Langhorne, PA 19047, United States&fuel_type=ELEC&radius=100.0&status=E&limit=10' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
To use this API, send a request with parameters such as location, boundary and radius.
The EV Charge Locator API provides data on electric vehicle charging stations and related information.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API returns information such as station location, fuel type, accessibility, operational status, contact details, available connectors, opening hours, last updated date, and the number of charging ports, enabling users to find and utilize electric vehicle charging stations effectively.
1,000 requests per hour in all plans.
The GET Stations Finder endpoint returns detailed information about charging stations, including geographic location, fuel types, operational status, access hours, and connector types. It also provides aggregate data such as total station counts and specific details for each station found within the specified search parameters.
Key fields in the response data include latitude, longitude, location_country, total_results, station_counts (with breakdowns by fuel type), and fuel_stations (which lists individual station details). These fields help users understand the availability and specifics of charging stations in the queried area.
The response data is structured in a JSON format, with top-level fields for geographic coordinates and total results. It includes nested objects for station counts and an array for fuel_stations, where each station's details are encapsulated, allowing for easy parsing and integration into applications.
The GET Stations Finder endpoint accepts parameters such as location (address formats), fuel_type (specific fuel types), radius (search area in miles), status (filter by operational status), and limit (maximum results returned). These parameters allow users to customize their queries effectively.
The GET Stations Finder endpoint provides information on station locations, fuel types, operational status, connector types, access hours, and contact details. This comprehensive data helps users locate and utilize charging stations based on their specific needs.
Users can utilize the returned data by parsing the JSON response to extract relevant information, such as finding the nearest charging stations, checking their availability, and understanding the types of connectors offered. This data can be integrated into navigation apps or EV management systems for enhanced user experience.
Data accuracy is maintained through regular updates and quality checks from reliable sources, including government databases and industry partners. This ensures that users receive current and precise information about charging stations and their operational status.
Typical use cases include integrating the API into mobile apps for EV drivers to locate nearby charging stations, providing real-time availability updates, and assisting fleet management systems in optimizing routes based on charging infrastructure.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
913ms
Service Level:
100%
Response Time:
1,199ms
Service Level:
100%
Response Time:
2,871ms
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
532ms
Service Level:
100%
Response Time:
89ms
Service Level:
100%
Response Time:
82ms
Service Level:
100%
Response Time:
624ms
Service Level:
100%
Response Time:
214ms
Service Level:
100%
Response Time:
642ms
Service Level:
100%
Response Time:
613ms
Service Level:
100%
Response Time:
1,328ms
Service Level:
100%
Response Time:
643ms
Service Level:
100%
Response Time:
958ms
Service Level:
100%
Response Time:
2,611ms
Service Level:
100%
Response Time:
144ms
Service Level:
100%
Response Time:
732ms
Service Level:
100%
Response Time:
1,189ms
Service Level:
100%
Response Time:
2,231ms
Service Level:
100%
Response Time:
216ms