Skip to main content
Appenda
Sign inDownload

Make your first API call.

The Appenda API reads and changes the tables, records and enrichment runs in a cloud workspace. Every request is HTTPS, sends JSON and answers JSON. This page takes you from no key to a working call in four steps.

1. Create an API key

  1. Sign in at appenda.app/account and open API keys.
  2. Pick the workspace, type a name and choose Create key.
  3. Copy the secret. It is shown once.

The key belongs to that workspace, so every request with it reaches that workspace. No workspace id goes in the path.

2. Save the key in your shell

export APPENDA_API_KEY="appenda_sk_live_..."

3. List your tables

curl https://api.appenda.app/v1/tables \
  -H "Authorization: Bearer $APPENDA_API_KEY"

4. Read the reply

{
  "data": [
    {
      "id": "tbl_67ad65ba34a7bbfc643711b8531cba3f",
      "name": "Series B SaaS accounts",
      "created_at": "2026-09-14T09:12:44.000Z",
      "updated_at": "2026-10-21T13:58:02.000Z"
    }
  ],
  "meta": {
    "next_cursor": null,
    "has_more": false
  }
}

Everything you asked for is under data. A list also says whether there is another page; see Pagination.

Next steps

  • Authentication: key kinds, rotation and revoking.
  • Errors: what a refused request looks like and how to retry.
  • Status: whether the API is up right now.
  • API reference: every operation, with a request you can copy in curl and other languages.

FAQs

I get 401. What is wrong?
The key is missing, mistyped or revoked. Check that the header reads exactly Authorization: Bearer followed by the key, with no quotes around the key.
I get 403 or 404 for a workspace I can see in the app.
A workspace key only reaches the workspace it was created in, and an id from another workspace answers 404. Check that the ids you send belong to the key's workspace.
Do local workspaces have an API?
No. The API reaches cloud workspaces. On the desktop, agents use MCP instead.