Page 140 of 218
Ordered by reported HTTPS, CORS support, no-auth access, then changed/observed facts. Access signals are not a popularity or quality score.
Box Platform provides functionality to provide access to content stored within Box. It provides endpoints for basic manipulation of files and folders, management of users within an enterprise, as well as more complex topics such as legal holds and retention policies.
Cloud Services · Unknown · HTTPS not confirmed
This document describes the Intellifi Brain Web API specification using the OpenAPI specification. The Brain Web API is a RESTful API that allows you to interact with the Intellifi devices and services in a powerful and simple way. Our end-to-end solution allows you to localize your items/assets based on technologies such as RFID and Bluetooth. # Try it out! The API can be tried out and tested using the 'api-doc/tryitout' endpoint on this site. This UI allows anyone to visualize and interact with the API’s resources without having any of the implementation logic in place. It’s automatically generated from this Specification, with the visual documentation making it easy for back end implementation and client side consumption. # Authentication Applications are required to provide some form of authentication to the API for every secured endpoint. The Brain offers two forms of authentication. - API key (Via an HTTP request header or URL parameter) - Session cookie --> # See also - About Intellifi and what we do: intellifi.nl - Technical and background information: intellifi.zendesk.com
Development · Unknown · HTTPS not confirmed
Welcome to the official API of the brainbi platform. Using this API you can freely integrate our analytics platform with any other solution. Please refer to the following documentation and in case of any issues, please contact us at service@brainbi.net. Please note: for this API you will use your email and password from the brainbi.net platform to gather a Bearer Token for any API calls (use Login and get token). Once you are finished with your calls, please do a logout to remove your token and keep your account safe (use logout).
Shopping · Unknown · HTTPS not confirmed
The Amazon Braket API Reference provides information about the operations and structures supported in Amazon Braket. Additional Resources: Amazon Braket Developer Guide
Cloud Services · Unknown · HTTPS not confirmed
Branch Locator API: API definition published in the OpenAPI directory for hsbc.com. See the linked specification for supported operations.
Finance · 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
Allows sellers to: 1) Load products definitions to the BrandLovers marktplace. 2) Receive and update orders status. 3) Receive and update shipping information. 4) Receive and update customer tickets. All requests consume and return application/json content. All request must be authenticated and use HTTPS.
Shopping · Unknown · HTTPS not confirmed
# Braze API Overview Braze provides a high performance REST API to allow you to track users, send messages, export data, and more. A REST API is a way to programmatically transfer information over the web using a predefined schema. Braze has created many different endpoints with specific requirements that will perform various actions and/or return various data. API access is done using HTTPS web requests to your company's REST API endpoint (this will correspond to your Dashboard URL as shown in the table below). Customers using Braze's EU database should use `https://rest.fra-01.braze.eu/`. For more information on REST API endpoints for customers using Braze's EU database see our EU/US Implementation Differences documentation. ## Braze Instances Instance | Dashboard URL | REST Endpoint ----------- |---------------- | -------------------- US-01 | `https://dashboard.braze.com` or `https://dashboard-01.braze.com` | `https://rest.iad-01.braze.com` US-02 | `https://dashboard-02.braze.com` | `https://rest.iad-02.braze.com` US-03 | `https://dashboard-03.braze.com` | `https://rest.iad-03.braze.com` US-04 | `https://dashboard-04.braze.com` | `https://rest.iad-04.braze.com` US-06 | `https://
Business · Unknown · HTTPS not confirmed
bridgedb webservices: API definition published in the OpenAPI directory for bridgedb.org. See the linked specification for supported operations.
Development · Unknown · HTTPS not confirmed
The Browse API has the following resources: item_summary: Lets shoppers search for specific items by keyword, GTIN, category, charity, product, or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values. (Experimental) search_by_image: Lets shoppers search for specific items by image. You can refine the results by using URI parameters and filters. item: Lets you retrieve the details of a specific item or all the items in an item group, which is an item with variations such as color and size and check if a product is compatible with the specified item, such as if a specific car is compatible with a specific part. Provides a bridge between the eBay legacy APIs, such as Finding, and the RESTful APIs, which use different formats for the item IDs. (Experimental) shopping_cart: Provides the ability for eBay members to see the contents of their eBay cart, and add, remove, and change the quantity of items in their eBay cart. Note: This resource is not available in the eBay API Explorer. The item_summary, search_by_image, and item resource calls require an Application access token. The shopping_cart resource calls requi
Shopping · Unknown · HTTPS not confirmed
Take screenshots of any website in real time
Development · Unknown · HTTPS not confirmed
# Budgea Development Guides Welcome to **Budgea**'s documentation. This documentation is intended to get you up-and-running with our APIs and advise on the implementation of some regulatory aspects of your application, following the DSP2's guidelines. ## Getting Started **IMPORTANT** Depending on your status with regard of the DSP2 regulation, **agent** or **partner**, you may call our APIs or simply use our Webview and callbacks to get the financial data of your users. As an **agent**, you are allowed to call directly our APIs and implement your own form to get the user's credentials. As a **partner**, you cannot manipulate the credentials, and have to delegate this step to us through our webview. The sections below will document how to use our APIs, make sure you have the **agent** status to do so. For the **partner**, please refer to the section *Webview* and *Callbacks* of this documentation. ### Overview Your API is a REST API which requires a communication through https to send and receive JSON documents. During your tests, we recommend to make calls to the API with curl or any other HTTP client of your choice. You can watch a video demonstration on this URL. For the examples
Finance · Unknown · HTTPS not confirmed
Social media management for marketers and agencies
Social · Unknown · HTTPS not confirmed
Bulk Data Storage System (BDSS) allows the public to discover, search, and download patent and trademark data in bulk form.
Development · Unknown · HTTPS not confirmed
Domain API (WHOIS, Check, Batch)
Development · Unknown · HTTPS not confirmed
## Overview The JSON REST API allows you to submit and receive BulkSMS messages. You can also get access to past messages and see your account profile. The base URL to use for this service is `https://api.bulksms.com/v1`. The base URL cannot be used on its own; you must append a path that identifies an operation and you may have to specify some path parameters as well. Click here to go to the main BulkSMS developer site. In order to give you an idea on how the API can be used, some JSON snippets are provided below. Have a look at the messages section for more information. Probably the most simple example ``` { "to": "+27001234567", "body": "Hello World!" } ``` You can send unicode automatically using the `auto-unicode` query parameter. Alternatively, you can specify `UNICODE` for the `encoding` property in the request body. Please note: when `auto-unicode` is specified and the value of the `encoding` property is `UNICODE`, the message will always be sent as `UNICODE`. Here is an example that sets the `encoding` explicitly ``` { "to": "+27001234567", "body": "Dobrá práce! Jak se máš?", "encoding": "UNICODE" } ``` You can also specify a from number ``` { "from": "+27007654321", "to":
Development · Unknown · HTTPS not confirmed
These endpoints constitute the functionality exposed by Bungie.net, both for more traditional website functionality and for connectivity to Bungie video games and their related functionality.
Media · Unknown · HTTPS not confirmed
***UPDATE:*** *We have released a beta version of the new bunq API documentation.* ***NOTICE:*** *We have updated the sandbox base url to `https://public-api.sandbox.bunq.com/v1/`. Please update your applications accordingly. Check here: for more info.* ***PSD2 NOTICE:*** *The second Payment Services Directive (PSD2) may affect your current or planned usage of our public API, as some of the API services are now subject to a permit. Please be aware that using our public API without the required PSD2 permit is at your own risk and take notice of our updated API Terms and Conditions on for more information.* # Introduction Welcome to bunq! - The bunq API is organised around REST. JSON will be returned in almost all responses from the API, including errors but excluding binary (image) files. - Please configure your implementation to send its API requests to `https://public-api.sandbox.bunq.com/v1/` - There is a version of the Android app that connects to the bunq Sandbox environment. To create accounts for the Sandbox app, please follow the steps in the Android Emulator section. ## Getting started Before you start sending API requests, you need to get an API key and activate it. API ac
Finance · Unknown · HTTPS not confirmed
Bus stop information, route and schedule data, and bus positions.
Development · Unknown · HTTPS not confirmed
The Business Profile Performance API allows merchants to fetch performance reports about their business profile on Google. Note - If you have a quota of 0 after enabling the API, please request for GBP API access.
Analytics · Unknown · HTTPS not confirmed
# Introduction The Business Registries API is built on HTTP. The API is RESTful. It has predictable resource URIs. The API is documented in OpenAPI format. In addition to the standard OpenAPI syntax we use a few vendor extensions . # Overview The following sections describe the resources that make up the Business Registries REST API. ## Current Version By default, all requests to https://api.abr.ato.gov.au receive the `v1` version of the REST API. We encourage you to explicitly request this version via the `Accept` header. Accept: application/vnd.abr-ato.v1+json ## Schema All API access is over HTTPS, and accessed from https://api.abr.ato.gov.au. All data is sent and received as JSON. Blank fields are included. All dates use the ISO 8601 format: YYYY-MM-DD For example: `2017-07-01` (the 1st of July 2017) All timestamps use the ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ For example: `2017-07-01T11:05:06+10:00` ## Timezones Some requests allow for specifying timestamps or generate timestamps with time zone information. We apply the following rules, in order of priority, to determine timezone information for API calls. ### Explicitly provide an ISO 8601 timestamp with timezone information
Finance · Unknown · HTTPS not confirmed
Retrieve Business Unit information.
Development · Unknown · HTTPS not confirmed
The Marketing API retrieves eBay products based on a metric, such as Best Selling, as well as products that were also bought and also viewed.
Shopping · Unknown · HTTPS not confirmed
Manipulates events and other calendar data.
Analytics · Unknown · HTTPS not confirmed