Business APIs — page 3

Native Ads Publisher API

Business

This is a Native Ads Publisher API it provides same functionality as Native Ads Publisher Account GUI.

Adobe Experience Manager (AEM) API

Business

Swagger AEM is an OpenAPI specification for Adobe Experience Manager (AEM) API

CompanyAPI

Business

Automatisera onboarding, compliance och leverantörskontroll med tillförlitlig data, löpande övervakning och bättre beslutsunderlag.

Fitbit Plus API

Business

# Overview The Fitbit Plus API is a RESTful API. The requests and responses are formated according to the [JSON API](http://jsonapi.org/format/1.0/) specification. In addition to this documentation, we also provide an [OpenAPI](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md) "yaml" file describing the API: [Fitbit Plus API Specification](swagger.yaml). # Authentication Authentication for the Fitbit Plus API is based on the [OAuth 2.0 Authorization Framework](https://tools.ietf.org/html/rfc6749). Fitbit Plus currently supports grant types of **client_credentials** and **refresh_token**. See [POST /oauth/token](#operation/createToken) for details on the request and response formats. <!-- ReDoc-Inject: <security-definitions> --> ## 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 (patient, coach, or admin) to login and have access to data which is appropriate to that specific user. It is possible to build such an application, but it is not possible to use Fitbit Plus as a federated identity provider. You would need to have a separate means of verifying a user's identity. We do not currently support the required password-based oauth flow to make this possible. # Paging The Fitbit Plus API supports two different pagination strategies for GET collection endpoints. #### Skip-based paging Skip-based paging uses the query parameters `page[size]` and `page[number]` to specify the max number of resources returned and the page number. We default to skip-based paging if there are no page parameters. The response will include a `links` object containing links to the first, last, prev, and next pages of data. If the contents of the collection change while you are iterating through the collection, you will see duplicate or missing documents. For example, if you are iterating through the `calender_event` resource via `GET /pub/calendar_event?sort=start_at&page[size]=50&page[number]=1`, and a new `calendar_event` is created that has a `start_at` value before the first `calendar_event`, when you fetch the next page at `GET /pub/calendar_event?sort=start_at&page[size]=50&page[number]=2`, the first entry in the second response will be a duplicate of the last entry in the first response. #### Cursor-based paging Cursor-based paging uses the query parameters `page[limit]` and `page[after]` to specify the max number of entries returned and identify where to begin the next page. Add `page[limit]` to the parameters to use cursor-based paging. The response will include a `links` object containing a link to the next page of data, if the next page exists. Cursor-based paging is not subject to duplication if new resources are added to the collection. For example, if you are iterating through the `calender_event` resource via `GET /pub/calendar_event?sort=start_at&page[limit]=50`, and a new `calendar_event` is created that has a `start_at` value before the first `calendar_event`, you will not see a duplicate entry when you fetch the next page at `GET /pub/calendar_event?sort=start_at&page[limit]=50&page[after]=<cursor>`. We encourage the use of cursor-based paging for performance reasons. In either form of paging, you can determine whether any resources were missed by comparing the number of fetched resources against `meta.count`. Set `page[size]` or `page[limit]` to 0 to get only the count. It is not valid to mix the two strategie

ID4i API

Business

Domain registriert bei united-domains.de

Vestorly API

Business

Vestorly Developers API

Startup-directory research and weekly product leaderboard data

Logo API for brands, stocks, and cryptocurrencies

Search businesses and points of interest by city, deduplicated with a coverage report

Software pricing for 512 tools with the source URL and the date each price was read

API for B2B company data enrichment, domain enrichment, and website enrichment

B2B contact and company enrichment: verified work emails, mobile numbers, firmographics, technologies in use and hiring signals

Manage business locations, sync listings across publishers, respond to reviews, publish posts, and pull local search analytics

LinkedIn Email Finder and Email Verifier

Cost, timeline and complexity estimates for website, ecommerce and app projects

Resolve any B2B identityin milliseconds

Global customs manifest and bill of lading APIs across 10 sovereign nations

US property data API — Zestimate, photos, taxes, price history

Webhooks API

Business

Provides a way for apps to subscribe to certain change events in HubSpot. Once configured, apps will receive event payloads containing details about the changes at a specified target URL. There can only be one target URL for receiving event notifications per app.

Data on 7,000+ AI products across 29 markets, with market scores and shut-down and acquisition records

Technology stack of any website, and every site running a given technology, across 399M+ sites