List your tables
Every table in your organization's projects, open ones by default. Use a table's `id` with the table endpoints. Tables are shared across the organization.
Every table in your organization's projects, open ones by default. Use a table's id with the table endpoints. Tables are shared across the organization.
API key (sk_live_... prefix). Generate keys in the UI under Settings > API Keys, then send it as Authorization: Bearer sk_live_...
In: header
Query Parameters
Only this project's tables
uuidtrue adds closed tables
"true" | "false"Response Body
application/json
application/json
curl -X GET "https://loading/api/v1/tables"{
"data": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "string",
"entity_type": "string",
"row_mode": "string",
"project": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "string"
},
"archived_at": "string",
"created_at": "string",
"updated_at": "string"
}
]
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}Search the enterprise signals feed GET
Enterprise catalog-wide signals feed -- the same underlying data and query shape as GET /news, but accessible via session, OAuth, or API-key auth (not API-key-only), and gated by the `signals` module entitlement instead of `news_signals`. Org must have the Signals Feed module enabled; otherwise responds 403 entitlement_required.
A district table as CRM records GET
What Bellwork's CRM sync sends to Salesforce or Freshsales, for a CRM that pulls: per row, the district as an account (its match key, NCES ID and the table's answers as fields) and its people. `fields` names every field a record can carry. Each record's `hash` changes only when the record does, so a scheduled job can skip unchanged rows. Rows come in the table's order. Only district tables. See the Your own CRM guide.