Skip to main content

Documentation Index

Fetch the complete documentation index at: https://dev.1st.app/llms.txt

Use this file to discover all available pages before exploring further.

You don’t need to be a developer to use the 1st API. You just need to talk to an AI.
1

Create an API key

Sign in at dashboard.1st.app, open Integrations → API access, click Create API key.
  • Name it something you’ll recognize, “Sheets dashboard”, “Hudl sync”, “Coach’s Airtable script”.
  • Pick Read only unless your integration needs to rename devices or tag them. Most integrations are read-only.
  • Pick an expiry. 90 days is a good default; rotate keys at least yearly.
Copy the key the moment it appears. It’s shown once, then never again. Store it in a password manager or your tool’s secret settings.
If your key ever ends up somewhere you don’t fully control. a chat message, a shared doc, a screenshot, revoke it from the same page and create a fresh one. Revocation takes effect within seconds.
2

Ask an AI to build your integration

Open Claude or ChatGPT. Paste this prompt, filling in what you actually want:
Read https://dev.1st.app/llms-full.txt. That's the full reference
for the 1st sensor platform API.

Then build me a [Google Apps Script | Airtable Script | Bubble
plugin | n8n workflow | Python script] that
[pulls last night's CO2 readings for every device into a sheet |
 flags rooms above 1000 ppm and emails the coach |
 syncs device data into my Hudl player profiles].

The API key is in [PropertiesService.ST_API_KEY | env var
ST_API_KEY | Airtable secret config]. Don't put the key in the
code itself.
The AI will read the docs and write working code on the first try. If something looks off, paste the error message back and say “fix this”, the error messages from our API are designed to tell the AI exactly what to change.
3

Paste the generated code into your tool

Wherever the AI told you the code goes:
  • Google Sheets. Extensions → Apps Script
  • Airtable. Automations → Run script
  • Bubble. Backend workflows → API plugin
  • n8n / Make. Code node or HTTP Request node
  • Custom Python, save as pull.py, set ST_API_KEY, run python3 pull.py
Set your API key as an environment variable or secret in the tool (the AI will tell you how, but the key never goes in the code itself).Run it. Data lands wherever you asked.

​
What the AI will probably write

Just so you know what to expect, here’s roughly what comes back when you ask for “a Python script that fetches the current readings for every device”: 
import os, requests

API_KEY = os.environ["ST_API_KEY"]
BASE = "https://api.1st.app/v1"

resp = requests.get(
    f"{BASE}/devices/current",
    headers={"Authorization": f"Bearer {API_KEY}"},
)
resp.raise_for_status()

for d in resp.json()["data"]:
    name = d["display_name"] or d["device_id"]
    latest = d["latest"] or {}
    co2 = latest.get("co2_ppm")
    temp = latest.get("temp_c")
    print(f"{name}: CO2 {co2} ppm, {temp}°C")
You don’t need to write this. You don’t need to read it carefully. You just paste it where the AI told you to put it.

​
Common integrations

​
Live dashboard in Google Sheets

Paste this into a Sheets cell, replacing the key with your own: 
=IMPORTDATA("https://api.1st.app/v1/readings.csv?last=7d&shape=wide&key=1st_sk_...")
last=7d gives you the last 7 days. Change it to last=24h for the last day, last=30d for the last month — whatever you want. shape=wide returns one row per timestamp with one column per (device × metric), the layout spreadsheets actually want. Save the sheet and it refreshes automatically.
URLs with ?key=... get logged everywhere they go (Sheets share panel, your browser history, anyone who sees your screen). Create a dedicated key per spreadsheet so rotating it is cheap.

​
Tag a device with your AMS player ID

Ask the AI: 
Read https://dev.1st.app/llms-full.txt.

Write a one-off Python script that calls PATCH /v1/devices/{id} on
device 8a72a1c7-3c91-4f5b-b39e-1d2c4e3f5a7b to tag it with
hudl_player_id=12345 and position=GK. My read_write key is in env
var ST_API_KEY_RW.
You’ll get back a script you can run once and forget. After tagging, you can find the device by your AMS ID anytime: 
GET https://api.1st.app/v1/devices?metadata.hudl_player_id=12345

​
Next

Build with AI

Five copy-paste prompts that build complete integrations.

Endpoint reference

Every endpoint, every parameter, every response shape.

AMS integration

Map devices to your players via metadata.

Spreadsheet recipes

Apps Script templates and direct IMPORTDATA examples.