> ## Documentation Index
> Fetch the complete documentation index at: https://docs.photon.codes/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use Stable documentation by default. Honor an explicit Beta request or a URL under /docs/beta/. If the requested version conflicts with the installed CLI package or API origin, clarify the target before writing integration code.
> Pages under /docs/beta/ document Beta; other product pages document Stable. Keep the CLI package, commands, API origin, and credentials within the selected version. State the documentation version in your answer.
> For MCP search, always pass version: Stable or version: Beta. Unfiltered search mixes both versions. For filesystem reads, keep Beta queries under /beta/ and exclude /beta/ from Stable queries; discover paths before reading them.
> The public docs base is https://photon.codes/docs. Convert MCP page paths to public URLs under that base, preserving /beta/ when present. Read https://photon.codes/docs/skill.md for version selection and https://photon.codes/docs/llms.txt for the version indexes.

# Connect Telegram bot

> Connect Telegram bot: connectTelegramBot in the TypeScript, Python and Rust clients.

`POST /v1/projects/{id}/platforms/telegram/bots`

Starts a free managed Telegram bot connection. Each project may have one unfinished Telegram provision, including user interaction and failure cleanup. A different Idempotency-Key while one is active returns 409 TELEGRAM\_PROVISION\_IN\_PROGRESS with its operationId and operationUrl; resume it, cancel it while cancellation is available, or wait for it to finish. Rejected keys remain reusable. Open detail.setupUrl to connect an existing managed bot or create a new one with the project's default agent name or a custom display name, then poll Location. The link remains usable while the operation is active and never expires. Replaying the same Idempotency-Key returns the original operation, even after completion or while a newer setup is active. POST, GET and list share the same operation details. The API includes detail.setupUrl only for callers with platforms:write for the project; read-only callers receive the other details unchanged.

<Tabs>
  <Tab title="TypeScript">
    ```typescript TypeScript theme={null}
    photon.projects.platforms.connectTelegramBot(input: ConnectTelegramBotInput, options?: RequestOptions): Promise<ConnectTelegramBotOutput>
    ```
  </Tab>

  <Tab title="Python">
    ```python Python theme={null}
    photon.projects.platforms.connect_telegram_bot(input: ConnectTelegramBotInput) -> models.Operation
    ```
  </Tab>

  <Tab title="Rust">
    ```rust Rust theme={null}
    client.connect_telegram_bot(idempotency_key: String, id: String, body: &types::ConnectTelegramBotRequest).await -> Result<ResponseValue<types::Operation>, Error<ConnectTelegramBotError>>
    ```
  </Tab>
</Tabs>

<RequestExample>
  ```typescript TypeScript theme={null}
  import { Photon } from "@photon-ai/api";

  const photon = new Photon({
    headers: { Authorization: `Bearer ${process.env.PHOTON_API_TOKEN}` },
  });
  const result = await photon.projects.platforms.connectTelegramBot({
    path: {
      id: "id",
    },
    headers: {
      idempotencyKey: "idempotencyKey",
    },
    body: {},
  });
  ```

  ```python Python theme={null}
  import os

  from photon_api import Photon
  from photon_api.rpc_generated import ConnectTelegramBotInput

  photon = Photon(headers={"Authorization": f"Bearer {os.environ['PHOTON_API_TOKEN']}"})
  result = photon.projects.platforms.connect_telegram_bot(
      ConnectTelegramBotInput.model_validate({
          "path": {
              "id": "id",
          },
          "headers": {
              "Idempotency-Key": "idempotencyKey",
          },
          "body": {},
      })
  )
  ```

  ```rust Rust theme={null}
  use photon_ai_api::{Credential, PhotonClientBuilder, SecretString};

  let token = std::env::var("PHOTON_API_TOKEN")?;
  let client = PhotonClientBuilder::new()
      .credential("accountServiceKey", Credential::Bearer(SecretString::from(token)))
      .build()?;
  let result = client
      .connect_telegram_bot(
          "idempotencyKey".to_owned(),
          "id".to_owned(),
          &serde_json::from_value(serde_json::json!({}))?,
      )
      .await
      .map_err(|error| format!("{error:?}"))?
      .into_inner();
  ```
</RequestExample>

<ResponseExample>
  ```json 202 theme={null}
  {
    "cancellable": true,
    "createdAt": "2026-01-01T00:00:00.000Z",
    "detail": {},
    "endedAt": "2026-01-01T00:00:00.000Z",
    "error": {
      "code": "string",
      "detail": "string"
    },
    "operationId": "string",
    "projectId": "string",
    "reason": "charge_refused",
    "resourceId": "string",
    "resourceType": "string",
    "startedAt": "2026-01-01T00:00:00.000Z",
    "state": "pending",
    "type": "resource.provision",
    "updatedAt": "2026-01-01T00:00:00.000Z"
  }
  ```
</ResponseExample>

## Parameters

<ParamField header="Idempotency-Key" type={"string"} required>
  Identifies one logical mutation across retries.
</ParamField>

<ParamField path="id" type={"string"} required />

## Body

## Returns

**`202`** Setup accepted. Open detail.setupUrl and poll the operation. Operation

Headers: `Location`. The raw response carries these headers; see [Raw responses](/docs/beta/api-client/raw-responses).

<ResponseField name="cancellable" type={"boolean"} required />

<ResponseField name="createdAt" type={"string (date-time)"} required />

<ResponseField name="detail" type={"object"} />

<ResponseField name="endedAt" type={"string (date-time)"} />

<ResponseField name="error" type={"OperationError"} />

<ResponseField name="operationId" type={"string"} required />

<ResponseField name="projectId" type={"string"} required />

<ResponseField name="reason" type={"OperationReason"} />

<ResponseField name="resourceId" type={"string"} />

<ResponseField name="resourceType" type={"string"} required />

<ResponseField name="startedAt" type={"string (date-time)"} />

<ResponseField name="state" type={"OperationState"} required />

<ResponseField name="type" type={"OperationType"} required />

<ResponseField name="updatedAt" type={"string (date-time)"} required />


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.