Page 19 of 38
Ordered by reported HTTPS, CORS support, no-auth access, then changed/observed facts. Access signals are not a popularity or quality score.
Let your users search the Internet by face! Integrate FaceCheck facial search seamlessly with your app, website or software platform. FaceCheck's REST API is hassle-free and easy to use. For code examples visit https://facecheck.id/Face-Search/API
Development · Unknown · HTTPS not confirmed
A full featured Facts API. REST access with json/xml/jsonp result support. On this day birth and death support, random fact, keyword search support etc. Below is the documentation for the Random Facts API calls. You can try them out right here. Click here to subscribe
Development · Unknown · HTTPS not confirmed
A RESTful webservice to request a railway journey - FREE plan with restricted access (max. 10 requests per minute). Please ignore the message in the API Console about the access token. Register to use an less restricted version, which requires an access token.
Development · Unknown · HTTPS not confirmed
Generate random fake identities (name, address, email, phone , credit card info etc). Click here to subscribe
Development · Unknown · HTTPS not confirmed
Multimodal travel API to return modes of transportation between cities and points of interest.
Development · Unknown · HTTPS not confirmed
A RESTful webservice to retrieve data about the operational state of public elevators and escalators in german railway stations.
Development · Unknown · HTTPS not confirmed
Welcome to the File Storage API. You can use this API to access all File Storage API endpoints. ## Base URL The base URL for all API requests is `https://unify.apideck.com` We also provide a Mock API that can be used for testing purposes: `https://mock-api.apideck.com` ## Headers Custom headers that are expected as part of the request. Note that RFC7230 states header names are case insensitive. | Name | Type | Required | Description | | --------------------- | ------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | x-apideck-consumer-id | String | Yes | The id of the customer stored inside Apideck Vault. This can be a user id, account id, device id or whatever entity that can have integration within your app. | | x-apideck-service-id | String | No | Describe the service you want to call (e.g., pipedrive). Only needed when a customer has activated multiple integrations for the same Unified API. | | x-apideck-raw | Boolean | No | Include raw response. Mostly used for debugging purposes. | | x-apideck-app-id | String | Yes | The application id of your Unify a
Development · Unknown · HTTPS not confirmed
Upload and manage files.
Development · Unknown · HTTPS not confirmed
Files.com API: API definition published in the OpenAPI directory for files.com. See the linked specification for supported operations.
Development · Unknown · HTTPS not confirmed
FCM send API that provides a cross-platform messaging solution to reliably deliver messages at no cost.
Development · Unknown · HTTPS not confirmed
FishEye: API definition published in the OpenAPI directory for fisheye.local. See the linked specification for supported operations.
Development · Unknown · HTTPS not confirmed
Fisheye Crucible: API definition published in the OpenAPI directory for fecru.local. See the linked specification for supported operations.
Development · Unknown · HTTPS not confirmed
# Overview The Fitbit Plus API is a RESTful API. The requests and responses are formated according to the JSON API specification. In addition to this documentation, we also provide an OpenAPI "yaml" file describing the API: Fitbit Plus API Specification. # Authentication Authentication for the Fitbit Plus API is based on the OAuth 2.0 Authorization Framework. Fitbit Plus currently supports grant types of **client_credentials** and **refresh_token**. See POST /oauth/token for details on the request and response formats. --> ## Building Integrations We will provide customers with unique client credentials for each application/integration they build, allowing us to enforce appropriate access controls and monitor API usage. The client credentials will be scoped to the organization, and allow full access to all patients and related data within that organization. These credentials are appropriate for creating an integration that does one of the following: - background reporting/analysis - synchronizing data with another system (such as an EMR) The API credentials and oauth flows we currently support are **not** well suited for creating a user-facing application that allows a user (patien
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, if you are not returning any results try with big cities/airports like LON (London) or NYC (New-York).
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, to see what is included in test please refer to our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, to see what is included in test please refer to our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, to see what is included in test please refer to our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, to see what is included in test please refer to our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, if you are not returning any results try with big cities/airports like LON (London) or NYC (New-York).
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, to see what is included in test please refer to our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, this API in test only returns a few selected cities. You can find the list in our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, this API in test only returns a few selected cities. You can find the list in our **data collection**.
Development · Unknown · HTTPS not confirmed
Before using this API, we recommend you read our **Authorization Guide** for more information on how to generate an access token. Please also be aware that our test environment is based on a subset of the production, if you are not returning any results try with big cities/airports like LON (London) or NYC (New-York).
Development · Unknown · HTTPS not confirmed