<aside> ⚠️ These docs are for the v1 version of the Felt API, which is undergoing deprecation. We encourage everyone to switch to our API v2.

</aside>

What Is The Felt API?

The main way for users to create maps and upload data is directly inside the Felt app. However, software developers may choose to interact with Felt programmatically, enabling them to create maps and upload data via code.

Requests to the Felt API all start like this:

<https://felt.com/api/v1>

Authorizing Requests

Requests to the Felt API must include a special authorization header like this:

authorization: Bearer <access token>

Types of Authorization

There are two ways of authorizing requests to the Felt API:

• Personal Access Tokens: the easiest way of using the Felt API. Personal Access Tokens can be created directly in your User page, under the Integrations tab.

  generating_personal_auth_token.mp4

• OAuth 2.0: for developers building user-facing applications, Felt also provides authentication via OAuth. This is a more complex flow that is only available for approved integrations.

  Learn more in the OAuth Authentication and authorization ****section of the (DEPRECATED) Felt Public API reference page.

What Can I Do With The Felt API?

Identifying A Map ID

Requests that are aimed to a specific Felt map require knowing that map’s ID. The map ID is the part of a URL that goes after the map title and before the query parameters.

For instance, in the following URL:

<https://felt.com/map/Felt-API-Map-Elements-SssjclTrScGmH4TfPHzNjD?loc=27.07,-41.06,3z>

The map ID would be the part after the last dash: SssjclTrScGmH4TfPHzNjD.