# Get recon report PDF

> The monthly report as the PDF One's report page downloads, built on the server from the same report data and layout.

Source: https://docs.vigilbase.com/one/api/reference/customers/get-customers-id-recon-reports-report-id-pdf

`GET https://one.vigilbase.com/api/customers/{id}/recon/reports/{reportId}/pdf`

The monthly report as the PDF One's report page downloads, built on the server from the same report data and layout. Same access as reading the report. Used by the iOS app.

## Authorizations

Send one of these:

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`.
- `Authorization` (string, header, required): Organisation API key (`vb_one_…`) from **Settings → API keys** in Vigilbase One, sent as `Authorization: Bearer vb_one_…`. Read-only keys work. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).
- Permissions checked: `read:customers`

## Path parameters

- `id` (string, required)
- `reportId` (string, required)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or an API key (vb_one_…)
curl --request GET \
  --url 'https://one.vigilbase.com/api/customers/{id}/recon/reports/{reportId}/pdf' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```