> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/developers/oauth-2.0-for-approved-partners.md).

# OAuth 2.0 for approved partners

Approved integration partners can have users sign in with their PaintScout login instead of pasting an API Key. Contact PaintScout with your redirect URLs. We create an OAuth application for you and send you a Client ID, plus a Client Secret for a server-side app.

<details>

<summary>Flow, endpoints and token details</summary>

Use the OAuth 2.0 Authorization Code flow. Apps that cannot keep a secret (native, desktop, browser-only) must use PKCE.

| Value         |                                                                      |
| ------------- | -------------------------------------------------------------------- |
| Authorize URL | `https://auth.paintscout.com/authorize`                              |
| Token URL     | `https://auth.paintscout.com/oauth/token`                            |
| `audience`    | `https://openapi.paintscout.com` (required on the authorize request) |
| Scopes        | `openid email profile`, plus `offline_access` for a refresh token    |

Send the access token as `Authorization: Bearer <access_token>`, the same header an API Key uses. The token acts as the user who signed in, within that user's company and permissions.

The token works on this API only; other PaintScout APIs reject it. Your application is authorized for this `audience` only. Redirect URLs must match exactly; we do not register wildcards.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.paintscout.com/developers/oauth-2.0-for-approved-partners.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
