---
title: "Download a resignation letter"
method: GET
path: "/v1/resignations/{offboarding_request_id}/resignation-letter"
tags: ["Resignations"]
---

# Download a resignation letter

`GET /v1/resignations/{offboarding_request_id}/resignation-letter`

## Request

- Base URL: `https://gateway.remote.com`
- URL: `https://gateway.remote.com/v1/resignations/{offboarding_request_id}/resignation-letter`
- Auth: one of:
  - OAuth 2
    - Authorization code: `/auth/oauth2/authorize`
    - Token URL: `/auth/oauth2/token` scopes: `https://gateway.remote.com/company.manage`
  - OAuth 2
    - Authorization code: `/auth/oauth2/authorize`
    - Token URL: `/auth/oauth2/token` scopes: `resignation_letter:read`
  - OAuth 2
    - Authorization code: `/auth/oauth2/authorize`
    - Token URL: `/auth/oauth2/token` scopes: `all:read`
  - OAuth 2
    - Authorization code: `/auth/oauth2/authorize`
    - Token URL: `/auth/oauth2/token` scopes: `all:write`
  - OAuth 2
    - Client credentials
    - Token URL: `/auth/oauth2/token` scopes: `resignation_letter:read`
  - OAuth 2
    - Client credentials
    - Token URL: `/auth/oauth2/token` scopes: `all:read`
  - OAuth 2
    - Client credentials
    - Token URL: `/auth/oauth2/token` scopes: `all:write`
  - HTTP bearer

Downloads a resignation letter from an employment request.

## Authentication

This endpoint accepts any one of the following token types:

- **Company-scoped access token** (`OAuth2AuthorizationCode`) — obtained by a company manager through the Authorization Code flow or the Refresh Token flow. See [Authentication for partners](https://developer.remote.com/docs/authentication-for-partners).
- **Company-scoped access token (assertion)** (`OAuth2CompanyManagerAssertion`) — obtained through the `urn:ietf:params:oauth:grant-type:jwt-bearer` grant for a company manager. See [OAuth Assertion](https://developer.remote.com/docs/authorization-method-oauth-assertion).
- **Customer API token** (`CustomerAPIToken`) — generated by the customer on their Integration Settings page, with the scopes they choose there. See [Authorization for customers](https://developer.remote.com/docs/authorization-for-customers).

## Scopes

Any one of the scopes in a token type's row is enough. `all:read` and `all:write` work too.

| Token type | Category | Read only Scope | Write only Scope (read access implicit) |
|---|---|---|---|
| Company-scoped access token | Manage employment documents (`employment_documents`) | View resignation letters (`resignation_letter:read`) | - |
| Company-scoped access token (assertion) | Manage employment documents (`employment_documents`) | View resignation letters (`resignation_letter:read`) | - |
| Customer API token | Manage employment documents (`employment_documents`) | View resignation letters (`resignation_letter:read`) | - |

## Path parameters

- `offboarding_request_id` string, required

## Response `200`

Success

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `422`: Unprocessable Entity
- `429`: Unprocessable Entity

---

[API](https://skmtc.dev/remote-com/apis/offboarding.md) - [All operations](https://skmtc.dev/remote-com/apis/offboarding/llms.txt) - [OpenAPI document](https://skmtc.dev/remote-com/apis/offboarding/revisions/f0d3f7cbc9dd?raw)