Mock sample for your project: City of Surrey Traffic Loop Count API.
Integrate with "City of Surrey Traffic Loop Count API." from surrey.ca in no time with Mockoon's ready to use mock sample
City of Surrey Traffic Loop Count API.
Version: 0.1
Speed up your application development by using "City of Surrey Traffic Loop Count API." ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
Description
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.
Other APIs by surrey.ca
Other APIs in the same category
Movie Reviews API
With the Movie Reviews API, you can search New York Times movie reviews by keyword and get lists of NYT Critics' Picks.
United India Insurance Company Limited
apisetu.gov.in
United India Insurance Co. Ltd. is a Public Sector General Insurance Company incorporated in 1938, having its presence all over India providing risk cover to 1.74 Crore policyholders. General Insurance Policies such as Motor, Health, Personal Accident, Travel, e.t.c issued by United India Insurance Co. Ltd. (https://uiic.co.in/) are available to be downloaded by citizens of India to their DigiLocker account.
Motor Vehicle Department, Nagaland
apisetu.gov.in
Driving License (DL) and Vehicle Registration Certificate (RC) of the State, as available on Parivahan Sewa (http://parivahan.co.in/) of Ministry of Road Transport and Highways, are available on DigiLocker. Citizens can pull these documents into their DigiLocker accounts.
COVID-19 data API
covid19-api.com
Transport Department, Mizoram
apisetu.gov.in
Driving License (DL) and Vehicle Registration Certificate (RC) of the State, as available on Parivahan Sewa (http://parivahan.co.in/) of Ministry of Road Transport and Highways, are available on DigiLocker. Citizens can pull these documents into their DigiLocker accounts.
U.S. EPA Enforcement and Compliance History Online (ECHO) - Enforcement Case Search
epa.gov
Enforcement and Compliance History Online (ECHO) is a tool developed and maintained by EPA's Office of Enforcement and Compliance Assurance for public use. ECHO provides integrated compliance and enforcement information for over 1 million regulated facilities nationwide.
CASE Rest Services provide multiple service endpoints, each with specific capabilities, to search and retrieve data on civil cases entered into the
Integrated Compliance Information System (ICIS) and criminal cases entered into the Summary of Criminal Prosecutions database.
See Enforcement Case Search Help (https://echo.epa.gov/help/enforcement-case-search-help) for additional information on searching civil and criminal cases.
\
The getcases, getmap, getqid, and getdownload end points are meant to be used together, while the enhanced getcaseinfo end point is self contained..
The recommended use scenario for getcases, getqid, getmap, and getdownoad is:
\
1) Use getcases to validate passed query parameters, obtain summary statistics and to obtain a queryid (QID). QIDs are time sensitive and will be valid for approximately 30 minutes.
2) Use get_qid, with the returned QID, to paginate through arrays of case results.
3) Use get_map, with the returned QID, to zoom in/out and pan on the clustered and individual facility coordinates, related to the returned cases, that meet the QID query criteria.
4) Use get_download, with the returned QID, to generate a Comma Separated Value (CSV) file of facility information that meets the QID query criteria.
\
In addition to the service endpoints listed above there are two detailed case report services, one for civil cases (getcasereport) and one for criminal cases (getcrcasereport).
See the Civil Enforcement Case Report Help (https://echo.epa.gov/help/reports/enforcement-case-report-help) and the Criminal Case Report Help (https://echo.epa.gov/help/reports/criminal-case-report-help) for additional information
on then data returned from these two services.
\
Additional ECHO Resources: Web Services, About ECHO's Data, Data Downloads
CASE Rest Services provide multiple service endpoints, each with specific capabilities, to search and retrieve data on civil cases entered into the
Integrated Compliance Information System (ICIS) and criminal cases entered into the Summary of Criminal Prosecutions database.
See Enforcement Case Search Help (https://echo.epa.gov/help/enforcement-case-search-help) for additional information on searching civil and criminal cases.
\
The getcases, getmap, getqid, and getdownload end points are meant to be used together, while the enhanced getcaseinfo end point is self contained..
The recommended use scenario for getcases, getqid, getmap, and getdownoad is:
\
1) Use getcases to validate passed query parameters, obtain summary statistics and to obtain a queryid (QID). QIDs are time sensitive and will be valid for approximately 30 minutes.
2) Use get_qid, with the returned QID, to paginate through arrays of case results.
3) Use get_map, with the returned QID, to zoom in/out and pan on the clustered and individual facility coordinates, related to the returned cases, that meet the QID query criteria.
4) Use get_download, with the returned QID, to generate a Comma Separated Value (CSV) file of facility information that meets the QID query criteria.
\
In addition to the service endpoints listed above there are two detailed case report services, one for civil cases (getcasereport) and one for criminal cases (getcrcasereport).
See the Civil Enforcement Case Report Help (https://echo.epa.gov/help/reports/enforcement-case-report-help) and the Criminal Case Report Help (https://echo.epa.gov/help/reports/criminal-case-report-help) for additional information
on then data returned from these two services.
\
Additional ECHO Resources: Web Services, About ECHO's Data, Data Downloads
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.
Geocoder REST API
This API represents address cleaning, correction, completion, geocoding, reverse geocoding, and proximity resources for intersection addresses, physical addresses and their occupants in British Columbia. Please read our data collection notice.
Please note that you may experience issues when submitting requests to the delivery or test environment if using this OpenAPI specification in other API console viewers.
Developer API keys are unique and can be acquired with a GitHub account. Production government applications may use organization API keys acquired by contacting DataBC. API keys are further described in the Developer guide.
Notification: If you have applications or web pages that link to the BC Address Geocoder you must use the following URL.
https://geocoder.api.gov.bc.ca
Please note that the following URLs were deprecated in September 2018 More Details.
http://apps.gov.bc.ca/pub/geocoder
https://apps.gov.bc.ca/pub/geocoder
\
\
Please note that you may experience issues when submitting requests to the delivery or test environment if using this OpenAPI specification in other API console viewers.
Developer API keys are unique and can be acquired with a GitHub account. Production government applications may use organization API keys acquired by contacting DataBC. API keys are further described in the Developer guide.
Notification: If you have applications or web pages that link to the BC Address Geocoder you must use the following URL.
https://geocoder.api.gov.bc.ca
Please note that the following URLs were deprecated in September 2018 More Details.
http://apps.gov.bc.ca/pub/geocoder
https://apps.gov.bc.ca/pub/geocoder
\
\
vs API
Introduction
This API returns data regarding almost all nouns in vedic literature. The results are JSON objects that contain the word transliterated to the Roman script, the word in the Nagari script, the meaning of the word, and the category the word belongs to. Proper nouns are not included (yet).
The API uses the Swagger 2.0 specification.
Authentication
This is an open API.
Try it out
This sandbox can be used to get data for only one kind of resource, that is, to fetch data for a string contained in the meaning of any of the words.
The remaining resources work a similar fashion. For details, see the reference documentation.
This API returns data regarding almost all nouns in vedic literature. The results are JSON objects that contain the word transliterated to the Roman script, the word in the Nagari script, the meaning of the word, and the category the word belongs to. Proper nouns are not included (yet).
The API uses the Swagger 2.0 specification.
Authentication
This is an open API.
Try it out
This sandbox can be used to get data for only one kind of resource, that is, to fetch data for a string contained in the meaning of any of the words.
The remaining resources work a similar fashion. For details, see the reference documentation.