> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.console/settings/developers/oauth2.md).

# OAuth2

<figure><img src="/files/YA4quKgfewuq1j8NXSnC" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You need Client Id and Client Secret in order to identify the client requesting for authentication. Those credentials let any 3rd party service authenticate with the Access Token URI. It is used to identify the request as coming from expected and trusted source.
{% endhint %}

## Table contents

There are 4 specific columns:

* Name
* Client ID
* Client Secret
* URLs

## Create New Token

<figure><img src="/files/uai3R7K7aKoYXCPCgIE0" alt=""><figcaption></figcaption></figure>

* **Name** – we recommend to use web services names up to 64 symbols.
* **Redirect URLs** – add up to 11 (click **Add URL** and **Bin** buttons) URLs to external web services

## Actions

* **Hover Client ID** or **Secret** to view it – hint will appear, click **Copy** pictogram to put it to your clipboard
* **Actions Menu**
  * **Edit** – (also can be accessed by click on row area) opens *Token modal window*
  * **Delete** – opens delete modal window. Follow the steps described there.


---

# 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://docs.blynk.io/en/blynk.console/settings/developers/oauth2.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.