> ## Documentation Index
> Fetch the complete documentation index at: https://help.getvero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vero Track REST API

>  `v2.0.0` 

```bash API Base URL theme={null}
Live Server:https://api.getvero.com/api/v2
```

## Introduction

This documentation is for v2.0 of Vero's Track REST API. The URLs listed in this documentation are relative to `https://api.getvero.com/api/v2`.

This API is very stable. v2.0 was released prior to 2016 and there have been no breaking changes since that time.

### Sending data with requests

Unless otherwise specified, request data should be passed to the API as JSON objects via `POST`. The documentation for each API endpoint contains details of the parameters accepted by that endpoint.

### Supported ingest integrations

The majority of our customers use tools like [Segment](https://www.getvero.com/integrations/segment-source/) or [Rudderstack](https://www.getvero.com/integrations/rudderstack/) to track and send data to Vero Cloud.

See the full list of [Integrations](https://www.getvero.com/integrations/) for integrations that support this API. Use the "Data In: API" filter.

### Our SDKs

Refer to our [Developer Guide](/developer-docs/sdk) for more information on available SDKs.

Note that the request samples used in our API documentation are auto-generated and do not reference our SDKs.

### Questions or problems

Have questions or can't get something to work? Get in touch via [support@getvero.com](mailto:support@getvero.com).

## Authentication

Authentication against the Vero API is done using a valid Authentication Token. Authentication Tokens should be kept secret. They have the power to write data to your account and, in the future, will have the ability to read data too.

To generate and access API credentials visit [Settings](https://app.getvero.com/settings/project) in your Vero account.

Requests are authenticated by providing a parameter called `auth_token` with each request. This parameter must contain a valid and active Authentication Token.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail.

## Errors

Vero uses conventional HTTP response codes to indicate the success or failure of an API request.

Codes in the `2xx` range mean success, codes in the `4xx` mean there was an error in the data passed to Vero's API (such as missing parameters) and codes in the `5xx` range indicate an error with Vero's endpoint.

| Code                            | Description                     |
| :------------------------------ | :------------------------------ |
| **200 - OK**                    | The request was successful.     |
| **400 - Bad request**           | Bad request.                    |
| **401 - Unauthorized**          | Your credentials are invalid.   |
| **404 - Not Found**             | The resource doesn't exist.     |
| **50X - Internal Server Error** | An error occurred with our API. |