How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Amigo Context Graphs API

The Context Graphs API from Amigo — 4 operation(s) for context graphs.

Amigo Context Graphs API is one of 72 APIs that Amigo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Context Graphs. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 4 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 5 base URLs: https://api.amigo.ai, https://internal-api.amigo.ai, https://api-eu-central-1.amigo.ai, https://api-ap-southeast-2.amigo.ai, https://api-ca-central-1.amigo.ai.

8 operations 4 paths 31 schemas 1 DELETE4 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.amigo.ai
Authentication
HTTP Bearer, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

Amigo Context Graphs API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer-Authorization). An API key is passed in the header as X-ORG-ID (Bearer-Authorization-Organization). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

  • Bearer-Authorization — Amigo issued JWT token that identifies an user. It's issued either after logging in through the frontend, or manually through the [SignInWithAPIKey](sign-in-wi…
  • Bearer-Authorization-Organization — An optional organization identifier that indicates from which organization the token is issued. This is used in rare cases where the user to authenticate is ma…
  • Basic — The username should be set to {orgid}{userid}, and the password should be the Amigo issued JWT token that identifies the user.

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Context Graphs 8
POST
/v1/{workspace_id}/context-graphs
Create a context graph
create-context_graph 1 param body → 201404409403401422
GET
/v1/{workspace_id}/context-graphs
List context graphs
list-context_graphs 5 params → 200404403401422
GET
/v1/{workspace_id}/context-graphs/{context_graph_id}
Get a context graph
get-context_graph 2 params → 200404403401422
PUT
/v1/{workspace_id}/context-graphs/{context_graph_id}
Update a context graph
update-context_graph 2 params body → 200404409403401422
DELETE
/v1/{workspace_id}/context-graphs/{context_graph_id}
Delete a context graph
delete-context_graph 2 params → 204404403401422
POST
/v1/{workspace_id}/context-graphs/{context_graph_id}/versions
Create a context graph version
create-context_graph-version 2 params body → 201404409403401422
GET
/v1/{workspace_id}/context-graphs/{context_graph_id}/versions
List context graph versions
list-context_graph-versions 5 params → 200404403401422
GET
/v1/{workspace_id}/context-graphs/{context_graph_id}/versions/{version}
Get a context graph version
get-context_graph-version 3 params → 200404403401422

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are ActionState-Output (16 properties), ActionState-Input (16 properties), ContextGraphVersionResponse (15 properties), DataCollectionState-Input (14 properties). Each schema is shown below with its type and property counts.

ExitCondition
object
3 properties 2 required
CreateContextGraphVersionRequest
object
9 properties 4 required
DecisionState-Output
object
Passthrough routing state — Agent picks an exit condition, no user interaction.
10 properties 4 required
DescriptionString
string
DataCollectionState-Input
object
Structured voice/text data collection with field tracking. The engine presents fields conversationally, tracks completion, and optionally falls back to a Surfa…
14 properties 5 required
ProgressHint
object
How the agent narrates waiting on a tool. deterministic=true: scripted — phrases play verbatim in order. deterministic=false: engine picks — phrases are hints.…
8 properties
ActionState-Input
object
User-facing engagement state with actions and exit conditions.
16 properties 8 required
NameString
string
ContextGraphVersionResponse
object
15 properties 15 required
DecisionState-Input
object
Passthrough routing state — Agent picks an exit condition, no user interaction.
10 properties 4 required
TurnPolicy
object
Voice pipeline parameters declared per HSM state. Lives on ActionState/DecisionState alongside guardrails, waitfor, and channeloverrides. The HSM state IS the…
10 properties
PaginatedResponse_ContextGraphResponse_
object
4 properties 2 required
CollectionField
object
A single field to collect during a data collection state.
8 properties 3 required
Guardrail
object
Typed safety rule enforced per-state (not just global freetext guidelines).
3 properties 2 required
HTTPValidationError
object
1 property
SearchString
string
ValidationError
object
5 properties 3 required
ToolCallSpec
object
A tool call that the agent can make in a state.
12 properties 1 required
PreloadSpec
object
A tool call executed deterministically by the engine on state entry. Unlike LLM-driven tool calls, preloads run before any LLM turn — the results appear in the…
2 properties 1 required
DataCollectionState-Output
object
Structured voice/text data collection with field tracking. The engine presents fields conversationally, tracks completion, and optionally falls back to a Surfa…
14 properties 5 required
ContextGraphResponse
object
8 properties 6 required
PaginatedResponse_ContextGraphVersionResponse_
object
4 properties 2 required
UpdateContextGraphRequest
object
2 properties
ActionState-Output
object
User-facing engagement state with actions and exit conditions.
16 properties 8 required
FailureClass
string
Why a tool result is a failure — produced by the executor at RUN time. Unlike ResultDelivery (a fixed config-time axis), this is a runtime classification the e…
Action
object
A single action the agent can take within a state.
2 properties 1 required
CreateContextGraphRequest
object
2 properties 1 required
ContextGraphState-Input
ChannelOverride
object
Per-channel behavior override for a state.
3 properties
AnnotationState
object
Injects a hardcoded inner thought (no LLM call).
4 properties 4 required
ContextGraphState-Output

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amigo-context-graphs-api-openapi.yml Raw ↑

Other APIs Amigo publishes across the network.

Amigo Account API
Amigo Admin API
Amigo Agent Definitions API
Amigo Agent Runs API
Amigo Agents API
Amigo Analytics API
Amigo API Keys API
Amigo Audit API
Amigo Auth API
Amigo Billing API
Amigo Calls API
Amigo Command Center API
Where this information came from

This is an independent, third-party profile of Amigo Context Graphs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.