# Visier Data Intake APIs API

> Visier Data Intake APIs API on Apizie: 9 endpoints (Retrieve a list of sources, Start a transfer session, Transfer data to sources via JSON, Cancel a transfer session, …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://www.apizie.tech/v1/open-data:visier-data-intake/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.

- Project key: `open-data:visier-data-intake`
- Category: Open Data
- Status: byok
- Source: https://visier.com
- Page: https://www.apizie.tech/api/open-data/visier-data-intake
- OpenAPI: https://www.apizie.tech/api/open-data/visier-data-intake/openapi.json

Visier APIs for sending raw or untransformed source data to Visier

## Endpoints

### Retrieve a list of sources
`GET https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-get-sources` (byok)

### Start a transfer session
`POST https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-start-transfer` (byok)

### Transfer data to sources via JSON
`POST https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-push-data` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| transferSessionId | string | yes | The transfer session ID returned after the data transfer session starts. |
| sourceId | string | no | The unique identifier associated with the source you want to transfer data to. |
| sequence | integer | no | The unique sequence number associated with a batch of records. |
| tenantCode | string | no | The code of the tenant you want to transfer data to. For example, WFF_j1r or WFF_j1r~c7o. |
| body | object | yes | JSON request body |

### Cancel a transfer session
`POST https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-push-data-cancel` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| transferSessionId | string | yes | The transfer session ID to cancel. |

### Transfer data to sources via file upload
`POST https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-upload-data` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| transferSessionId | string | yes | The transfer session ID returned after the data transfer session starts. |
| sourceId | string | no | The unique identifier associated with the source you want to transfer data to. |
| sequence | string | no | The unique sequence number associated with a batch of records. |
| tenantCode | string | no | The code of the tenant you want to transfer data to. For example, WFF_j1r or WFF_j1r~c7o. |
| body | object | yes | JSON request body |

### Retrieve processing job statuses by receiving job ID
`GET https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-get-processing-jobs-by-parent-receiving-job-id` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| receivingJobId | string | yes | The receiving job ID. |
| tenantCode | string | no | The tenant code of the tenant you want to retrieve the processing jobs for. Use this if you are only interested in the results for one… |
| limit | integer | no | The limit of processing jobs to retrieve per page. |
| start | integer | no | The index to start retrieving results from, also known as offset. The index begins at 0. |

### Complete a transfer session
`POST https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-push-data-complete` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| body | object | yes | JSON request body |

### Retrieve a receiving job’s status
`GET https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-receiving-job-status` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| receivingJobId | string | yes | The **dataReceivingJobId** provided after a data transfer session completes. See **`/v1/op/jobs/receiving-jobs`**. |
| jobs | boolean | no | If true, returns the status of receiving jobs spawned by the receiving job specified by receivingJobId. |
| tenantCode | string | no | The tenant code of the tenant you want to retrieve the receiving jobs for. Use this if you are only interested in the results for one… |
| start | integer | no | The index to start retrieving results from, also known as offset. The index begins at 0. |
| limit | integer | no | The number of job statuses to return per page. |

### Upload a data file to Visier
`POST https://www.apizie.tech/v1/open-data:visier-data-intake/data-upload-file-to-visier` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| filename | string | yes | The filename of the data file to upload, including the file extension (such as .zip or .csv). |

## Example
```
curl "https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-get-sources" \
  -H "x-api-key: $APIZIE_KEY" \
  -H "x-upstream-key: $PROVIDER_KEY"
```

## FAQ

### How do I call the Visier Data Intake APIs API?
Create a free Apizie key, then send GET https://www.apizie.tech/v1/open-data:visier-data-intake/data-intake-get-sources with the header x-api-key. Every endpoint returns { project, data, timestamp }.

### Is the Visier Data Intake APIs API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Visier Data Intake APIs itself also needs your own key from {vanity-name}.api.visier.io.

### Can AI agents use the Visier Data Intake APIs API?
Yes. Add the Apizie MCP server (https://www.apizie.tech/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key open-data:visier-data-intake.

### What is the status of the Visier Data Intake APIs API?
Needs your own provider key (bring your own key)