<commit_before>---
title: Extract File
layout: reference
---

# Extract File  


## Description
The extracted data for the specified extract job. Formatted according to the associated extract definition.

## Version
1.0

## URI
`https://www.concursolutions.com/api/expense/extract/v1.0/{DefinitionID}/job/{JobID}/file `


## Operations
[GET](#get)


## <a name="get"></a>Get an extract file

###  Definition
Requests the extracted data for the specified extract job.

### Request

```xml
    GET https://www.concursolutions.com/api/expense/extract/v1.0/{DefinitionID}/job/{JobID}/file HTTP/1.1
    Authorization: OAuth {access token}
    ...
```

### Request parameters

#### Path parameters

| Parameter |Required/Optional| Description |
|-----------------|--------|-----------------------------|
| {_DefinitionID_}/job | Required. | The definition identifier and the job keyword. |
| job/{_JobID_}/file | Required. | The identifier for the job and the job and file keywords. |

Example: `https://www.concursolutions.com/api/expense/extract/v1.0/nYoPK$pZmcowMRUqcl5bnDAwwsMydyt$xd/job/uIo87jk3SHudi$sdlYle8$peot$pD21jyd/file` 

### Headers

#### Authorization header
Required. Authorization header with OAuth token for valid Concur user. The OAuth consumer must have one of the following user roles in Concur: Company Administrator or Web Services Administrator for Professional, or Can Administer for Standard. These roles allow the user to manage data for the entire company. 

#### Content-Type header
application/xml

###  Response

### Content types

* text/csv
* application/zip

### Response body

This request will return the extracted data in text/csv format if there was a single file produced or as a zip archive if the extract definition is configured to produce more than one file.

### Examples

###  XML example of response with single extract file

```xml
    200 OK
    Content-Type: text/csv
    100,AAA,BBBB,CCCC,...<rest of file>
```

###  XML example of successful response with multiple extract files

```xml
    200 OK
    Content-Type: application/zip
    <zip file contents>
```<commit_msg>Fixed 130<commit_after>---
title: Extract File
layout: reference
---

# Extract File  


## Description
The extracted data for the specified extract job. Formatted according to the associated extract definition.

## Version
1.0

## URI
`https://www.concursolutions.com/api/expense/extract/v1.0/{DefinitionID}/job/{JobID}/file `


## Operations
[GET](#get)


## <a name="get"></a>Get an extract file

###  Definition
Requests the extracted data for the specified extract job.

### Request

```
xml
    GET https://www.concursolutions.com/api/expense/extract/v1.0/{DefinitionID}/job/{JobID}/file HTTP/1.1
    Authorization: OAuth {access token}
    ...
```

### Request parameters

#### Path parameters

| Parameter |Required/Optional| Description |
|-----------------|--------|-----------------------------|
| {_DefinitionID_}/job | Required. | The definition identifier and the job keyword. |
| job/{_JobID_}/file | Required. | The identifier for the job and the job and file keywords. |

Example: `https://www.concursolutions.com/api/expense/extract/v1.0/nYoPK$pZmcowMRUqcl5bnDAwwsMydyt$xd/job/uIo87jk3SHudi$sdlYle8$peot$pD21jyd/file` 

### Headers

#### Authorization header
Required. Authorization header with OAuth token for valid Concur user. The OAuth consumer must have one of the following user roles in Concur: Company Administrator or Web Services Administrator for Professional, or Can Administer for Standard. These roles allow the user to manage data for the entire company. 

#### Content-Type header
application/xml

###  Response

### Content types

* text/csv
* application/zip

### Response body

This request will return the extracted data in text/csv format if there was a single file produced or as a zip archive if the extract definition is configured to produce more than one file.

### Examples

###  XML example of response with single extract file

```
xml
    200 OK
    Content-Type: text/csv
    100,AAA,BBBB,CCCC,...<rest of file>
```

###  XML example of successful response with multiple extract files

```
xml
    200 OK
    Content-Type: application/zip
    <zip file contents>
```
{'fraction_non_alphanumeric': 0.1323564169227133, 'fraction_numerical': 0.012999290947766485, 'mean_word_length': 3.59500542888165, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 6, 'lorem ipsum': 0, 'www.': 6, 'xml': 8}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4734383', 'n_tokens_mistral': 1248, 'n_tokens_neox': 1184, 'n_words': 429}