> For the complete documentation index, see [llms.txt](https://developerdocs.instructure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developerdocs.instructure.com/services/parchment-digital-badges/authentication.md).

# Authentication

## Authentication Methods

There are two primary ways to obtain an access token:

1. [Password-Based Authentication](/services/parchment-digital-badges/authentication/password-based-authentication.md): Use your username and password to obtain an access token.
2. [Authorization Code-Based Authentication](/services/parchment-digital-badges/authentication/authorization-code-based-authentication.md): Use OAuth2 to obtain an access token via an authorization code grant.

## Authenticating Requests

Once you obtained an access token from the Parchment Digital Badges API domain for your region, you'll need to provide an Authorization header of type "Bearer" for all additional requests. For example:

```bash
curl 'https://{BADGES_DOMAIN}/v2/users/self' -H "Authorization: Bearer YOURACCESSTOKEN"
```

## Token Expiration

Access tokens will expire, and if an expired token is used, a 401 status code will be returned.

The refresh token can be used to automatically renew an access token without requiring the password again. For example:

```bash
curl -X POST 'https://{BADGES_DOMAIN}/o/token' -d "grant_type=refresh_token&refresh_token=YOURREFRESHTOKEN"
```


---

# 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://developerdocs.instructure.com/services/parchment-digital-badges/authentication.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.