Mock sample for your project: Polling Places API
Integrate with "Polling Places API" from phila.gov in no time with Mockoon's ready to use mock sample
Polling Places API
phila.gov
Version: 1.0
Speed up your application development by using "Polling Places API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and allow you to stop relying on an external API to get the job done. No more API keys to provision, accesses to configure or unplanned downtime, just work.
Enhance your development infrastructure by mocking third party APIs during integrating testing.
Description
This data set contains the list of polling places. It can be organized by ward/division, accessibility rating, or type of building.
This list is used to assign poll workers, send the machines and necessary accessibility materials, etc.
Endpoint: http://api.phila.gov/polling-places/v1
Other APIs in the same category
UP State Council of Vocational Training, Uttar Pradesh, Uttar Pradesh
apisetu.gov.in
The State Council for Vocational Training (SCVT), Uttar Pradesh (http://www.vppup.in/) provides semester and consolidated mark sheets as well as vocational certificates for years 2013 to 2016.
Flinkster_API_NG
deutschebahn.com
This REST-API enables you to query for private transport sharing offers provided by companies and cities in Germany, Netherland and Austria.
You can search for informations about the rental stations (points or areas) where you can find the rentals by utilizing the /areas/ ressource.
With the help of the proximity search in the /bookingproposals/ URI you can request the availabilities of the rentalobjects for spontaneous or planed usage in the future.
Feel free to browse through data by setting the parameter 'providernetwork' to the value:
1: Search for car sharing offers provided by the Flinkster platform (http://www.flinkster.de)
2: Finding bike rental offers from Call a Bike (http://www.callabike.de)
You can find more details in the documentation section (Unfortunately only available in german language).
Have lots of fun and we are lucky to take notice of your products or getting your feedback.
You can search for informations about the rental stations (points or areas) where you can find the rentals by utilizing the /areas/ ressource.
With the help of the proximity search in the /bookingproposals/ URI you can request the availabilities of the rentalobjects for spontaneous or planed usage in the future.
Feel free to browse through data by setting the parameter 'providernetwork' to the value:
1: Search for car sharing offers provided by the Flinkster platform (http://www.flinkster.de)
2: Finding bike rental offers from Call a Bike (http://www.callabike.de)
You can find more details in the documentation section (Unfortunately only available in german language).
Have lots of fun and we are lucky to take notice of your products or getting your feedback.
City of Surrey Traffic Loop Count API.
This API provides locations of City of Surrey traffic loops and the corresponding traffic loop counts in 15 minute intervals. While the counts are broken up by 15 minute intervals, the data is currently loaded only once per day. We are hoping to increase this frequency to at least once every hour. The LOOP_ID field is common to both datasets and can be used to cross-reference them.
Available API endpoints
versioneye.com
VersionEye is a cross-platform search engine for free/libre/open source software libraries.
OpenTrials API
opentrials.local
TheTVDB API v3
thetvdb.com
API v3 targets v2 functionality with a few minor additions. The API is accessible via https://api.thetvdb.com and provides the following REST endpoints in JSON format.
How to use this API documentation
You may browse the API routes without authentication, but if you wish to send requests to the API and see response data, then you must authenticate.
Obtain a JWT token by POSTing to the /login route in the Authentication section with your API key and credentials.
Paste the JWT token from the response into the "JWT Token" field at the top of the page and click the 'Add Token' button.
You will now be able to use the remaining routes to send requests to the API and get a response.
Language Selection
Language selection is done via the Accept-Language header. At the moment, you may only pass one language abbreviation in the header at a time. Valid language abbreviations can be found at the /languages route..
Authentication
Authentication to use the API is similar to the How-to section above. Users must POST to the /login route with their API key and credentials in the following format in order to obtain a JWT token.
{"apikey":"APIKEY","username":"USERNAME","userkey":"USERKEY"}
Note that the username and key are ONLY required for the /user routes. The user's key is labled Account Identifier in the account section of the main site.
The token is then used in all subsequent requests by providing it in the Authorization header. The header will look like: Authorization: Bearer . Currently, the token expires after 24 hours. You can GET the /refresh_token route to extend that expiration date.
Versioning
You may request a different version of the API by including an Accept header in your request with the following format: Accept:application/vnd.thetvdb.v$VERSION. This documentation automatically uses the version seen at the top and bottom of the page.
How to use this API documentation
You may browse the API routes without authentication, but if you wish to send requests to the API and see response data, then you must authenticate.
Obtain a JWT token by POSTing to the /login route in the Authentication section with your API key and credentials.
Paste the JWT token from the response into the "JWT Token" field at the top of the page and click the 'Add Token' button.
You will now be able to use the remaining routes to send requests to the API and get a response.
Language Selection
Language selection is done via the Accept-Language header. At the moment, you may only pass one language abbreviation in the header at a time. Valid language abbreviations can be found at the /languages route..
Authentication
Authentication to use the API is similar to the How-to section above. Users must POST to the /login route with their API key and credentials in the following format in order to obtain a JWT token.
{"apikey":"APIKEY","username":"USERNAME","userkey":"USERKEY"}
Note that the username and key are ONLY required for the /user routes. The user's key is labled Account Identifier in the account section of the main site.
The token is then used in all subsequent requests by providing it in the Authorization header. The header will look like: Authorization: Bearer . Currently, the token expires after 24 hours. You can GET the /refresh_token route to extend that expiration date.
Versioning
You may request a different version of the API by including an Accept header in your request with the following format: Accept:application/vnd.thetvdb.v$VERSION. This documentation automatically uses the version seen at the top and bottom of the page.
Geographic API
The Geographic API extends the Semantic API, using a linked data approach to enhance location concepts used in The New York Times' controlled vocabulary and data resources which combine them with the GeoNames database, an authoritative and free to use database of global geographical places, names and features.
Polling Places API
phila.gov
This data set contains the list of polling places. It can be organized by ward/division, accessibility rating, or type of building.
This list is used to assign poll workers, send the machines and necessary accessibility materials, etc.
Endpoint: http://api.phila.gov/polling-places/v1
This list is used to assign poll workers, send the machines and necessary accessibility materials, etc.
Endpoint: http://api.phila.gov/polling-places/v1