> For the complete documentation index, see [llms.txt](https://api-docs.getflipturn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.getflipturn.com/authorization.md).

# Authorization

## Getting an API key

To create an API key, your user account must have "Owner"-level access. Log into Flipturn at [cloud.getflipturn.com](https://cloud.getflipturn.com/), go to Manage in the top navigation, select "API Keys" from the sidebar, and then click the "Create API Key" button.

API keys can be configured with limited access, so you can provision a key with access to only a specific site or subset of chargers.

## Using the API key

Once you have an API key, it should be passed in the `Authorization` header of the request, like so:

```sh
# Shell
curl "https://api.getflipturn.com/api/charging-sessions" -H "Authorization: Bearer {api_key}"
```

```js
// JavaScript
fetch('https://api.getflipturn.com/api/charging-sessions', {
  method: 'GET',
  headers: {
    Authorization: `Bearer ${apiKey}`,
  },
});
```

The API returns data in JSON format, along with an appropriate HTTP response code.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://api-docs.getflipturn.com/authorization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.