# Retrieve a Bundle

**GET** `/bundles/{bundleSlug}/`

Retrieve a Bundle by its slug. Optionally include additional related data such as form field data,
audit events, and downloadable files using the `include` query parameter.

## Using the include parameter

The `include` parameter allows you to fetch related data in a single API call instead of making
separate requests to the `/data`, `/events`, and `/files` endpoints. This can significantly
reduce the number of API calls needed and improve performance.

### Examples:

**Basic bundle retrieval:**
```
GET /api/v2/bundles/abc123/
```

**Include form data only:**
```
GET /api/v2/bundles/abc123/?include=data
```

**Include events and files:**
```
GET /api/v2/bundles/abc123/?include=events,files
```

**Include all additional data:**
```
GET /api/v2/bundles/abc123/?include=data,events,files
```

### Data Availability

- **data**: Only available for completed bundles, unless early data access is enabled for your account
- **events**: Always available for any bundle
- **files**: Only available for completed bundles with final documents ready, unless early file access is enabled

When data or files are not available, the corresponding field will be `null` in the response.

## Request

### Parameters

- `bundleSlug` (path, required, string): The slug that uniquely identifies the Bundle
- `include` (query, string): Comma-separated list of additional data to include in the response.
Allows you to retrieve related information in a single request instead of making separate API calls.

Supported values:
- `data`: Include form field data entered by signers (same as /data endpoint)
- `events`: Include audit events for the bundle (same as /events endpoint)
- `files`: Include downloadable files for the bundle (same as /files endpoint)

Examples:
- `?include=data` - Include only form data
- `?include=events,files` - Include both events and files
- `?include=data,events,files` - Include all additional data

### Responses

- `200`: A Bundle object, optionally with additional included data
  - Content types: `application/json`
- `400`: Bad Request - Invalid include parameter values
  - Content types: `application/json`
- `404`: Not found response
  - Content types: `application/json`