# Connecting your system to Venzeo through the API

> Get the API key and API documentation for your developer, to export reports and sync places, projects and assets (integration, REST API).

Source: https://help.venzeo.com/en/article/connecting-your-system-through-the-api
Language: en
Updated: 2026-10-31

Only administrators can open the API documentation with the API key.

The Venzeo™ API connects your own system, such as an ERP, GIS or asset register, to Venzeo. Your system can download reports and keep places of interest, projects and assets up to date. The API works for every active organisation. A developer builds the connection. This page tells you what to hand over.

_Example:_ A waste-collection company copies new reports into its ERP every night and updates its list of bins from its asset register.

## Get the API key

1. Open the main menu. If it is collapsed, click **Show Menu**.
2. Expand **API for developers**. Until your organisation has used the API, this section is at the end of the menu with the label **Inactive**.
3. Choose **Show API documentation**. The documentation opens in a new tab, with your organisation's API key already applied.
4. On that page, run the report export request.
5. In the curl example of that request, copy the text after `Authorization: Bearer`. This is your API key.

> **Warning:** Treat the API key like a password. With it, anyone can read your reports and create, change and deactivate your places of interest, projects and assets. If the key leaks, write to support@venzeo.com immediately.

## What to send to your developer

- The public API documentation: `https://api-external-eu.venzeo.com/docs/external/d41d8cd98f00b204e9800998ecf8427e/`. It opens without signing in. The guide at its top describes the typical workflows and error codes.
- The API key, through a separate, secure channel.
- Which data the connection may read or change, for example only reports, or also places of interest.

## Points developers often miss

- Times are Unix timestamps in milliseconds.
- Fields without a value are left out of the response, not sent as `null`.
- When `POST` answers `409`, the record already exists, so send `PUT` instead.

To export reports without programming, see [Exporting filtered reports](https://help.venzeo.com/en/article/exporting-filtered-reports).