3824351 - How do I use the Extracts V1 API?

The Extracts V1 API is only applicable to extracts that are NOT synced to a batch in the payment manager. This means it should only be used in Concur Professional.

The API can be used to run a flat file extract job and retrieve the generated files. Only data for reports and invoices that have completed the approval process including the processor step are available for extraction in a flat file.

Through a series of calls, an application connector can GET the current extract definition list, then use the result to perform a POST to run the extract job of their choosing. Once the POST is successful, the connector can then GET the extract file. While a POST is running, it is not possible to send another request for another job. Please bear this in mind when setting up automated calls as overlap can lead to a hung job that will block the file processing until Concur Support releases it. If you are planning to automate this API then please always include a status check to make sure a POST has been completed before sending a new one.

Advantages of using the extracts API over the regular job execution from the UI include:

• Access to extract files using HTTP to move or manage the data as opposed to using a FTP site or downloading manually
• the ability to receive extract files throughout the day at a time of your choosing as opposed to once a day in a pre-set time frame for your entity
• in combination with custom extracts, you gain the ability to receive different files from different jobs at a time best suited to the team that processes the posting for that specific org unit or payment type as opposed to being limited to 1 shared job per job type

This article explains step by step how to use the Extracts V1 API , KBA , CON-INT , Integrations , Problem