**Source URL:** https://limited.veevavault.dev/vault-api/api-reference/19.1/logs/download-daily-api-usage.md

# Download Daily API Usage



Retrieve the API Usage log for a single day, up to 30 days in the past. The log contains information such as user name, user ID, remaining burst and daily limits, and the endpoint called. Users with the **Admin > Logs > API Usage Logs** permission can access these logs.

Note that the daily API Usage logs may have a delay of about 10 minutes. If your log does not include appropriate data, know that your data is not lost, it is just not yet populated.

The API Usage Logs are designed for troubleshooting burst or daily limits, and discovering which of your integrations are causing you to hit these limits. These logs should not be used for auditing, as they are not designed with the appropriate level of restrictions for auditing. For example, if an API request fails to enter the usage log, the API call is not prevented from executing, which would be required if this log was designed for auditing. In rare cases an API call may not show up as an entry in the API Usage Log, but know that all calls are accurately reflected in your burst and daily limit counts.

<Endpoint path="/api/{version}/logs/api_usage?date=YYYY-MM-DD" method="GET"></Endpoint>

## Headers {#headers}

Note that this `Accept` header only changes the format of the response in the case of an error. This does not change the file format of the download.

<FieldTable>
| Name | Description |
| --- | --- |
| `Accept` | `application/json` (default) or `application/xml` |
</FieldTable>

## Query Parameters {#query-parameters}

You can modify the request by using one or more of the following parameters:

<FieldTable>
| Name | Description |
| --- | --- |
| `date` | The day to retrieve the API Usage log. Date is in UTC and follows the format `YYYY-MM-DD`. Date cannot be more than 30 days in the past. |
| `log_format` | Optional: Specify the format to download. Possible values are `csv` or `logfile`. If omitted, defaults to `csv`. Note that this call always downloads a ZIP file, and this parameter will change the format of the file contained within the ZIP. |
</FieldTable>

## Request {#request}

<CodeExample title="">
```
curl -X GET -H "Authorization: {SESSION_ID}" \
https://myvault.veevavault.com/api/v18.1/logs/api_usage?date=2018-01-31 > file

```
</CodeExample>

## Response {#response}

<CodeExample title="">`Content-Type: application/octet-stream;charset=UTF-8
Content-Disposition: attachment;filename="response.zip"
`</CodeExample>

## Response Details {#response-details}

On SUCCESS, Vault retrieves the API Usage log from the specified date as a .ZIP file. The HTTP Response Header `Content-Type` is set to `application/octet-stream`. The returned CSV or Logfile includes the following data:



---

**Previous:** [Retrieve Complete Audit History for a Single Object Record](/vault-api/api-reference/19.1/logs/audit-history/retrieve-complete-audit-history-for-a-single-object-record)  
**Next:** [Jobs](/vault-api/api-reference/19.1/jobs)