---
title: "Tulip APIs"
slug: "work-with-apis"
status: "update"
updated: 2026-02-03T21:42:58Z
published: 2026-02-03T21:45:08Z
canonical: "support.tulip.co/work-with-apis"
---

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

# Work with APIs

*Get familiar with Tulip's APIs to access your Tulip data, generate content, and configure your instance.*

**Access Tulip's [API documentation here](https://support.tulip.co/apidocs).**

For those unfamiliar with APIs, read [Introduction to APIs](/r230/docs/api-introduction).

### When should you use an API?

You should use an API when you want to have an integration among Tulip and other software systems or access/change information in an App through a Connector, like creating a tulip table query or retrieving information about a station.

## Tulip's API Documentation

| Documentation Link | Use | Set Up |
| --- | --- | --- |
| [Table API](https://support.tulip.co/apidocs/list-aggregations-of-a-tulip-table) | Integrate external systems with Tulip Tables | [Table API guide](https://support.tulip.co/docs/table-api-guide) |
| [Users API](https://support.tulip.co/apidocs/apiusersv1roles) | Retrieves data, such as users, roles, and groups. | [Set up a Tulip API](https://support.tulip.co/docs/set-up-a-tulip-api) |
| [Operator API](https://support.tulip.co/apidocs/create-a-user) | Create operators using an external system | [Operator API guide](https://support.tulip.co/docs/operator-api-guide) |
| [Machine Attributes API](https://support.tulip.co/apidocs/list-tulip-machine-types-and-their-corresponding-machines) | Send data to a specific attribute of a Machine | [Use the Machine Attributes API](/r230/docs/how-to-use-the-machine-attributes-api) |
| [Stations API](https://support.tulip.co/apidocs/apistationsv1interfaces) | Manage and onboard new Stations | [Stations API guide](/r230/docs/how-to-use-the-stations-api) |

**Connectors**

**Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions.

- **HTTP Connectors** utilize HTTP API endpoints.
- **SQL Connectors** can enable connectivity with certain SQL databases.
- **MQTT Connectors** can connect to MQTT brokers for machine monitoring.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif)

**Tulip Tables**

**Tulip Tables** are a global location to store your production data. **Tables** are made up of **Records** (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview(1).gif)

**Machine**

A **Machine** is a digital representation of a physical datasource. Machines have **Attributes** that are updated through an OPC-UA Connector or the Tulip API.

**Station**

**Stations** are a digital representation of a physical place or device in your facility. Stations are 1:1 with **Interfaces (display devices)** running Tulip Player, but Stations can also be assigned **Edge Devices,** Tulip Vision Camera Configurations, Machines, and more.