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

# Stop typing

> Stop showing the typing bubble. You don't need this before sending: a sent message clears it on its own. Some phones keep showing the bubble for up to a minute after a stop that isn't followed by a message.

Typing shows only in a 1:1 iMessage conversation the contact has already messaged. Anywhere else the call answers `200` with `status: "ignored"` and an `ignored_reason`, and does nothing.

Idempotent: stopping when nothing is typing answers `200` `stopped`.

Counts toward the conversation-actions rate limit (300 a minute per account).

### Stop typing

**Method:** `DELETE` | **Endpoint:** `/v1/conversations/{conversation_id}/typing`

**Description:** Stop the typing bubble you started with [Start typing](https://docs.ibubbl.com/api-reference/conversations/start-typing.md), when you decide not to reply. You don't need it before sending: a message you send clears the dots on its own.

**Authentication:** API key in the `Authorization` header: `Authorization: Bearer ib_pk_<64 hex>`. Create keys in the dashboard under **Settings → API access**.

**Rate limit:** 300 conversation actions per 60 seconds per account, shared with tapbacks, mark read and start typing. Over that, `429 rate_limited` with a `Retry-After` header; see [Rate limits](https://docs.ibubbl.com/concepts/limits.md#rate-limits).

#### Request Body

None. The path parameter `conversation_id` is the conversation's ID (a UUID).

#### How it behaves

* **iBubbl stops at once; some phones take longer.** The dots may stay on the contact's iPhone for up to about a minute after a stop that isn't followed by a message. Sending a message always clears them straight away.
* **It's safe to call twice**, or when nothing is typing: the answer is `200` with `status: "stopped"`.
* **Never refused for a block or an opt-out.** In a group, an SMS or RCS conversation, or one the contact hasn't messaged yet, it answers `ignored` with the same `ignored_reason` as Start typing.

```bash cURL theme={null}
curl -X DELETE https://api.ibubbl.com/v1/conversations/3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d/typing \
  -H "Authorization: Bearer $IBUBBL_API_KEY"
```

```typescript TypeScript theme={null}
const conversationId = "3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d";

const res = await fetch(`https://api.ibubbl.com/v1/conversations/${conversationId}/typing`, {
  method: "DELETE",
  headers: { Authorization: `Bearer ${process.env.IBUBBL_API_KEY}` },
  signal: AbortSignal.timeout(10_000),
});

const data = await res.json();
if (!res.ok) throw new Error(`${res.status} ${data.detail?.error}`);
console.log(data.status);
```

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

import requests

API_KEY = os.environ["IBUBBL_API_KEY"]

conversation_id = "3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d"

res = requests.delete(
    f"https://api.ibubbl.com/v1/conversations/{conversation_id}/typing",
    headers={"Authorization": f"Bearer {API_KEY}"},
    timeout=10,
)
data = res.json()
if not res.ok:
    raise RuntimeError(f"{res.status_code} {data['detail']['error']}")
print(data["status"])
```

```json 200 OK theme={null}
{
  "conversation_id": "3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d",
  "typing": false,
  "status": "stopped",
  "ignored_reason": null,
  "expires_at": null
}
```

```json 404 Not Found theme={null}
{
  "detail": {
    "error": "not_found",
    "message": "Conversation not found"
  }
}
```

#### Responses

**200 OK**

The same fields as [Start typing](https://docs.ibubbl.com/api-reference/conversations/start-typing.md), with `typing: false` and `status` `stopped` (or `ignored`).

```json theme={null}
{
  "conversation_id": "3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d",
  "typing": false,
  "status": "stopped",
  "ignored_reason": null,
  "expires_at": null
}
```

**401 Unauthorized**

```json theme={null}
{
  "detail": {
    "error": "unauthorized",
    "message": "Invalid or revoked API key"
  }
}
```

Other `message` values: `Authorization Bearer token required`, `API key required (use Authorization: Bearer ib_pk_…)`, `Invalid API key format`, `Customer account not found`.

**403 Forbidden**

```json theme={null}
{
  "detail": {
    "error": "forbidden",
    "message": "Account is suspended"
  }
}
```

Your iBubbl account is suspended or cancelled (`message` is then `Account is cancelled`). Every API-key endpoint returns this.

**404 Not Found**

```json theme={null}
{
  "detail": {
    "error": "not_found",
    "message": "Conversation not found"
  }
}
```

Also returned for a malformed ID and a conversation that belongs to another account.

**429 Too Many Requests**

```json theme={null}
{
  "detail": {
    "error": "rate_limited",
    "message": "Too many conversation actions; wait 12s (limit 300 a minute per account)."
  }
}
```

Wait the `Retry-After` header's seconds, then call again.


## OpenAPI

````yaml DELETE /v1/conversations/{conversation_id}/typing
openapi: 3.1.0
info:
  title: iBubbl API
  version: v1
  description: >-
    The iBubbl REST API. Send iMessages, manage contacts, and subscribe to
    webhook events from your backend.


    Authenticate every request with a Bearer API key (`ib_pk_<hex>`) — generate
    one from your dashboard's API Access settings. See the
    [Authentication](/authentication) guide.
servers:
  - url: https://api.ibubbl.com
security:
  - BearerAuth: []
tags:
  - name: Messages
  - name: Contacts
  - name: Conversations
  - name: Webhooks
  - name: Inbound Events
paths:
  /v1/conversations/{conversation_id}/typing:
    delete:
      tags:
        - Conversations
      summary: Stop typing
      description: >-
        Stop showing the typing bubble. You don't need this before sending: a
        sent message clears it on its own. Some phones keep showing the bubble
        for up to a minute after a stop that isn't followed by a message.


        Typing shows only in a 1:1 iMessage conversation the contact has already
        messaged. Anywhere else the call answers `200` with `status: "ignored"`
        and an `ignored_reason`, and does nothing.


        Idempotent: stopping when nothing is typing answers `200` `stopped`.


        Counts toward the conversation-actions rate limit (300 a minute per
        account).
      operationId: v1_stop_typing_v1_conversations__conversation_id__typing_delete
      parameters:
        - name: conversation_id
          in: path
          required: true
          schema:
            type: string
            title: Conversation Id
      responses:
        '200':
          description: Typing stopped (or ignored).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TypingStatus'
        '401':
          description: Missing or invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '403':
          description: '`forbidden`: your iBubbl account is suspended or cancelled.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '404':
          description: Conversation not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '429':
          description: >-
            `rate_limited`: more than 300 conversation actions in 60 seconds
            from your account (all keys, and tapbacks, read and typing requests,
            count together; list requests have their own budget). Wait
            `Retry-After` seconds, then send the same request again.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
components:
  schemas:
    TypingStatus:
      properties:
        conversation_id:
          type: string
          title: Conversation Id
          description: The conversation.
        typing:
          type: boolean
          title: Typing
          description: Whether the typing bubble is on after this call.
        status:
          type: string
          enum:
            - started
            - stopped
            - ignored
          title: Status
          description: >-
            `started` (or kept going), `stopped`, or `ignored`: typing can't be
            shown here and nothing was done; see `ignored_reason`.
        ignored_reason:
          anyOf:
            - type: string
              enum:
                - group
                - not_imessage
                - no_chat
            - type: 'null'
          title: Ignored Reason
          description: >-
            `group` (not available in group conversations), `not_imessage` (the
            contact is on SMS or RCS), `no_chat` (the contact hasn't messaged
            this line yet). Null otherwise.
        expires_at:
          anyOf:
            - type: string
            - type: 'null'
          title: Expires At
          description: >-
            When the bubble stops unless you call again (UTC), 10 seconds after
            the call. Null unless `started`.
      type: object
      required:
        - conversation_id
        - typing
        - status
        - ignored_reason
        - expires_at
      title: TypingStatus
      example:
        conversation_id: 3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d
        expires_at: '2026-11-11T15:04:15.123Z'
        status: started
        typing: true
    ApiError:
      properties:
        detail:
          allOf:
            - $ref: '#/components/schemas/ApiErrorDetail'
          description: >-
            Error envelope. Every `/v1` error response wraps a stable `error`
            code and a human-readable `message` in `detail`.
      type: object
      required:
        - detail
      title: ApiError
      example:
        detail:
          error: validation_error
          message: >-
            Exactly one of contact_id, to, chat_guid, or participant_phones is
            required
    ApiErrorDetail:
      properties:
        error:
          type: string
          title: Error
          description: >-
            Stable machine-readable error code. Use this for branching logic in
            your integration; the human-readable `message` is subject to change.
            See the Error Reference for the catalog.
          examples:
            - validation_error
        message:
          type: string
          title: Message
          description: Human-readable description of what went wrong.
          examples:
            - >-
              Exactly one of contact_id, to, chat_guid, or participant_phones is
              required
      type: object
      required:
        - error
        - message
      title: ApiErrorDetail
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: ib_pk_<64 hex>
      description: >-
        Bearer API key. Format: `Authorization: Bearer ib_pk_<64 hex>` (70
        characters). Generate keys from Dashboard → Settings → API Access.

````

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