Account API
The Vonage Business Cloud Account API enables you to retrieve information about accounts. Your application must subscribe to the Provisioning API suite to use this API.
Development · Unknown · HTTPS not confirmed
Page 13 of 38
Ordered by reported HTTPS, CORS support, no-auth access, then changed/observed facts. Access signals are not a popularity or quality score.
The Vonage Business Cloud Account API enables you to retrieve information about accounts. Your application must subscribe to the Provisioning API suite to use this API.
Development · Unknown · HTTPS not confirmed
Enables users to manage their Vonage API Account by programmable means. More information is available here: .
Development · Unknown · HTTPS not confirmed
Welcome to the Accounting API. You can use this API to access all Accounting 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 appli
Development · Unknown · HTTPS not confirmed
The Accounts API is a collection of methods used to query a customer account. It allows the developer to retrieve account-related data such as the user account balance. It should be noted that regional variations may exist - so some fields may not be returned for certain territories.
Development · Unknown · HTTPS not confirmed
Our active docs provide the ability to test out your account and to see the responses to your queries. The services are RESTful, and are accessed using standard HTTP methods over a secure HTTPS channel. Requests and responses are currently sent in JSON format, and have a base URL of /v1.
Development · Unknown · HTTPS not confirmed
### The Internet of Things for Everyone The Adafruit IO HTTP API provides access to your Adafruit IO data from any programming language or hardware environment that can speak HTTP. The easiest way to get started is with an Adafruit IO learn guide and a simple Internet of Things capable device like the Feather Huzzah. This API documentation is hosted on GitHub Pages and is available at https://github.com/adafruit/io-api. For questions or comments visit the Adafruit IO Forums or the adafruit-io channel on the Adafruit Discord server. #### Authentication Authentication for every API request happens through the `X-AIO-Key` header or query parameter and your IO API key. A simple cURL request to get all available feeds for a user with the username "io_username" and the key "io_key_12345" could look like this: $ curl -H "X-AIO-Key: io_key_12345" https://io.adafruit.com/api/v2/io_username/feeds Or like this: $ curl "https://io.adafruit.com/api/v2/io_username/feeds?X-AIO-Key=io_key_12345 Using the node.js request library, IO HTTP requests are as easy as: ```js var request = require('request'); var options = { url: 'https://io.adafruit.com/api/v2/io_username/feeds', headers: { 'X-AIO-Key': '
Development · Unknown · HTTPS not confirmed
Airbyte Configuration API https://airbyte.io. This API is a collection of HTTP RPC-style methods. While it is not a REST API, those familiar with REST should find the conventions of this API recognizable. Here are some conventions that this API follows: * All endpoints are http POST methods. * All endpoints accept data via `application/json` request bodies. The API does not accept any data via query params. * The naming convention for endpoints is: localhost:8000/{VERSION}/{METHOD_FAMILY}/{METHOD_NAME} e.g. `localhost:8000/v1/connections/create`. * For all `update` methods, the whole object must be passed in, even the fields that did not change. Authentication (OSS): * When authenticating to the Configuration API, you must use Basic Authentication by setting the Authentication Header to Basic and base64 encoding the username and password (which are `airbyte` and `password` by default - so base64 encoding `airbyte:password` results in `YWlyYnl0ZTpwYXNzd29yZA==`). So the full header reads `'Authorization': "Basic YWlyYnl0ZTpwYXNzd29yZA=="`
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, in test this API only contains data from the United States, Spain, United Kingdom, Germany and India.
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.
Development · Unknown · HTTPS not confirmed
Returns all airports
Development · Unknown · HTTPS not confirmed
Akeneo PIM REST API: API definition published in the OpenAPI directory for akeneo.com. See the linked specification for supported operations.
Development · Unknown · HTTPS not confirmed
This is the Alerter System API playground. More documentation is available at the API Help Center . The "Available Authorizations" in the Authorize popup only applies to this playground web interface. Other authorizations are available for the actual API.
Development · Unknown · HTTPS not confirmed
This is the Anchore Engine API. Provides the primary external API for users of the service.
Development · Unknown · HTTPS not confirmed
API for a tool to craftsmen used to register working hours, material usage and quality assurance. # Endpoint The endpoint `https://app.apacta.com/api/v1` should be used to communicate with the API. API access is only allowed with SSL encrypted connection (https). # Authentication URL query authentication with an API key is used, so appending `?api_key={api_key}` to the URL where `{api_key}` is found within Apacta settings is used for authentication # Pagination If the endpoint returns a `pagination` object it means the endpoint supports pagination - currently it's only possible to change pages with `?page={page_number}` but implementing custom page sizes are on the road map. # Search/filter Is experimental but implemented in some cases - see the individual endpoints' docs for further explanation. # Ordering Is currently experimental, but on some endpoints it's implemented on URL querys so eg. to order Invoices by `invoice_number` appending `?sort=Invoices.invoice_number&direction=desc` would sort the list descending by the value of `invoice_number`. # Associations Is currently implemented on an experimental basis where you can append eg. `?include=Contacts,Projects` to the `/api/v1
Development · Unknown · HTTPS not confirmed
Web API for TL mobile and web app
Development · Unknown · HTTPS not confirmed
The API to Search and Understand Audio & Video Data.
Development · Unknown · HTTPS not confirmed
Create beautiful product and API documentation with our developer friendly platform.
Development · Unknown · HTTPS not confirmed
This API provides a range of functions to get back currency conversion rates and amounts based on current Mastercard currency conversion values.
Development · Unknown · HTTPS not confirmed
DocSpring is a service that helps you fill out and sign PDF templates.
Development · Unknown · HTTPS not confirmed
# Introduction Api2Pdf is a powerful PDF generation API with no rate limits or file size constraints. Api2Pdf runs on AWS Lambda, a serverless architecture powered by Amazon to scale to millions of requests while being up to 90% cheaper than alternatives. **Supports wkhtmltopdf, Headless Chrome, LibreOffice, and PDF Merge.** You can also generate barcodes with ZXING (Zebra Crossing). # SDKs & Client Libraries We've made a number of open source libraries available for the API - Python: https://github.com/api2pdf/api2pdf.python - .NET: https://github.com/api2pdf/api2pdf.dotnet - Nodejs: https://github.com/api2pdf/api2pdf.node - PHP: https://github.com/Api2Pdf/api2pdf.php - Ruby: (Coming soon) # Authorization Create an account at portal.api2pdf.com to get an API key. **Authorize your API calls** - GET requests, include apikey=YOUR-API-KEY as a query string parameter - POST requests, add **Authorization** to your header. ``` Authorization: YOUR-API-KEY ``` # Quickstart If you are looking for just a quick call to grab PDFs of a URL, you can do a GET request like: ``` https://v2018.api2pdf.com/chrome/url?url={UrlToConvert}&apikey={YourApiKey} ``` For more advanced usage and settings, see
Development · Unknown · HTTPS not confirmed
Apicurio Registry is a datastore for standard event schemas and API designs. Apicurio Registry enables developers to manage and share the structure of their data using a REST interface. For example, client applications can dynamically push or pull the latest updates to or from the registry without needing to redeploy. Apicurio Registry also enables developers to create rules that govern how registry content can evolve over time. For example, this includes rules for content validation and version compatibility. The Apicurio Registry REST API enables client applications to manage the artifacts in the registry. This API provides create, read, update, and delete operations for schema and API artifacts, rules, versions, and metadata. The supported artifact types include: - Apache Avro schema - AsyncAPI specification - Google protocol buffers - GraphQL schema - JSON Schema - Kafka Connect schema - OpenAPI specification - Web Services Description Language - XML Schema Definition **Important**: The Apicurio Registry REST API is available from `https://MY-REGISTRY-URL/apis/registry/v2` by default. Therefore you must prefix all API operation paths with `../apis/registry/v2` in this case. For
Development · Unknown · HTTPS not confirmed
Transform API Descriptions from/to various formats
Development · Unknown · HTTPS not confirmed