Amigo · Schema
CreateConversationRequest
CompanyArtificial IntelligenceHealthcareAI AgentsVoiceClinicalConversational AIFHIRElectronic Health RecordsHIPAA
Properties
| Name | Type | Description |
|---|---|---|
| service_id | string | |
| entity_id | object | |
| channel | object | |
| recipient | object | Destination address for an outbound conversation (E.164 for sms/imessage). Required for non-web. |
| use_case_id | object | Channel-manager use case the outbound conversation is sent through. Required for non-web; channel-manager resolves the sender (FROM) from it (never caller-supplied). Must be owned by this workspace. |
| instruction | object | Optional context steering what the agent opens with on an outbound conversation. |
| force_new | boolean | Outbound thread-keyed channels (sms/imessage) only: close any existing ACTIVE conversation on the computed provider thread (recipient + use case) before dispatching, so the opener materializes a brand |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/amigo/main/json-schema/amigo-create-conversation-request-schema.json",
"title": "CreateConversationRequest",
"x-generated": "2026-10-12",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/amigo-conversations-api-openapi.yml#/components/schemas/CreateConversationRequest",
"properties": {
"service_id": {
"type": "string",
"format": "uuid",
"title": "Service Id"
},
"entity_id": {
"anyOf": [
{
"type": "string",
"format": "uuid"
},
{
"type": "null"
}
],
"title": "Entity Id"
},
"channel": {
"$ref": "#/$defs/ChannelKind",
"default": "web"
},
"recipient": {
"anyOf": [
{
"$ref": "#/$defs/PhoneE164"
},
{
"type": "null"
}
],
"description": "Destination address for an outbound conversation (E.164 for sms/imessage). Required for non-web."
},
"use_case_id": {
"anyOf": [
{
"type": "string",
"format": "uuid"
},
{
"type": "null"
}
],
"title": "Use Case Id",
"description": "Channel-manager use case the outbound conversation is sent through. Required for non-web; channel-manager resolves the sender (FROM) from it (never caller-supplied). Must be owned by this workspace."
},
"instruction": {
"anyOf": [
{
"$ref": "#/$defs/BackgroundString"
},
{
"type": "null"
}
],
"description": "Optional context steering what the agent opens with on an outbound conversation."
},
"force_new": {
"type": "boolean",
"title": "Force New",
"description": "Outbound thread-keyed channels (sms/imessage) only: close any existing ACTIVE conversation on the computed provider thread (recipient + use case) before dispatching, so the opener materializes a brand-new conversation instead of continuing the old thread. Rejected with 422 on channel=web — every web create already starts a new conversation, so force_new is meaningless there.",
"default": false
}
},
"type": "object",
"required": [
"service_id"
],
"$defs": {
"BackgroundString": {
"type": "string",
"maxLength": 10000
},
"ChannelKind": {
"type": "string",
"enum": [
"voice",
"sms",
"whatsapp",
"email",
"web",
"imessage"
],
"title": "ChannelKind",
"description": "HSM execution channel type.\n\nDetermines how the HSM engine communicates with end users.\nEach kind maps to one or more providers."
},
"PhoneE164": {
"type": "string",
"maxLength": 16,
"minLength": 2
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/amigo-create-conversation-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.