AgentConnect
Integrations

Create a further agent’s own Teams bot

For a tenant that already serves another agent: with the ticket the connect step answered, create the agent’s bot (the blueprint’s principal if the tenant has none, the agent identity, its bot registration, and a proof token), publish its package to the tenant’s organization catalog, and install its row on the agent. Answers the integration, the administrator’s teams with the app’s state in each, and the ticket for the install step. Safe to repeat: a retry finds what an earlier attempt created. A tenant where the bot cannot be created answers 409 MSTEAMS_AGENT_BOTS_UNAVAILABLE with Microsoft’s reason.

POST
/v1/orgs/{orgId}/integrations/msteams/connect/agent-bot

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

orgId*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/orgs/string/integrations/msteams/connect/agent-bot" \  -H "Content-Type: application/json" \  -d '{    "ticket": "string"  }'
{  "integrationId": "string",  "agentId": "string",  "agentBot": true,  "request": {    "id": "string",    "agentId": "string",    "tenantId": "string",    "status": "pending",    "reason": "string",    "name": "string",    "createdAt": "string",    "adminCenterUrl": "string"  },  "authorizeUrl": "http://example.com",  "teams": [    {      "id": "string",      "name": "string",      "app": "updated"    }  ],  "ticket": "string",  "store": true}