API keys

Programmatic access to Harbor & Vine. Keys are scoped, shown once, and can be revoked at any time.

Keys

3 active · 1 revoked

Name	Key	Scopes	Created	Last used
Production server	`ak_live_9f2…`	`conversations:readreservations:write`	2 months ago	4 minutes ago
Toast sync	`ak_live_4c8…`	`reservations:readreservations:write`	last month	2 hours ago
Website widget	`ak_live_be1…`	`conversations:writeknowledge:read`	3 weeks ago	26 minutes ago
Analytics exportRevoked	`ak_live_77d…`	`analytics:read`	3 months ago	last month

Making a request

REST · JSON

Base URLhttps://api.alice.dev/v1

Example

curl -G "https://api.alice.dev/v1/conversations" \
  -H "Authorization: Bearer $ALICE_API_KEY" \
  -d "channel=voice" \
  -d "limit=20"

Every request needs an Authorization: Bearer header. Responses are JSON, paginated with cursor, and rate limited to 120 requests a minute per key.

Good practice

One key per integration, named after it. Revoking then costs you one service, not all of them.
Grant the narrowest scopes that work. Scopes are fixed at creation.
Keys belong to the organization, not to you — they survive someone leaving the team.
Rotate on a schedule: create the replacement, deploy it, then revoke the old key.