Integrations / Sierra
Sierra
Sierra Agent OS — no public usage/admin OpenAPI on apis.io yet. Coming soon.
API key
What Telara does
Capability matrix
Before you connect
Prerequisites
A Sierra workspace you can administer.
Admin. Do not paste a conversational agent token into Telara unless the Connect form exists for spend.
Vendor setup
Get the credential
1
Open organization settings
Sign in to Sierra as an admin. Open Organization → Settings → API (or the admin API keys page) if Sierra has enabled it for your contract.
2
Create an admin key only when the page exists
If Sierra shows an admin/usage API, create a key, copy it once, and paste it in Telara. If the page is missing, stop — this connector is reserved until spend_connector ships.
3
Paste in Telara
Settings → Integrations → Sierra. Paste only what the Connect form asks for. A bot runtime token is the wrong class.
In Telara
Connect in Telara
API key
Reserved until spend_connector ships.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API key
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
This catalog entry does not declare extra semantic-search exclusions.
After connect
Verify it worked
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty
Known limitations
This connector is reserved until Sierra’s spend API ships. Do not invent a paste-a-key flow.
Agent transcripts and admin usage are different credentials when both exist.