# Authentication

Source: https://docs.pitchpointsolutions.com/api/authentication/index/

**Stable**

## Authentication API

Sign in with the credentials PPS issues you, and exchange a refresh token for a new access token. Every other PPS API call carries the access token in an `Authorization: Bearer <token>` header.

An access token expires one hour after it is issued, and the refresh token expires on its own schedule. An unattended integration must be able to sign in again on its own, not just refresh.

> **API Reference:** [Obtaining An Access Token](https://docs.pitchpointsolutions.com/developer_guides/authentication/access_token/) walks through signing in, refreshing, and what to do when a refresh is rejected.

| Operation | Method and path | Reference |
|---|---|---|
| Sign In With Password | `POST /user-management-services-ws/oauth2/002/signInWithPassword` | [Sign In With Password](https://docs.pitchpointsolutions.com/api/authentication/signinwithpassword/) |
| Refresh Access Token | `POST /user-management-services-ws/oauth2/002/refreshIdToken` | [Refresh Access Token](https://docs.pitchpointsolutions.com/api/authentication/refreshidtoken/) |

These two paths sit under the user management service rather than the base URL the other APIs share, so send them to the host exactly as written above.