> ## Documentation Index > Fetch the complete documentation index at: https://docs.lazyapp.in/llms.txt > Use this file to discover all available pages before exploring further. # Update a conversation > Assign it to a team member, set its status, replace its tags, or set the workspace-level `archived` / `pinned` flags. Only the fields you send change. Assigning starts `human_assignment` workflows, and resolving or closing starts `conversation_closed` ones, exactly as in the inbox. **Required scope:** `messages:send` ## OpenAPI ````yaml /api-reference/openapi.json patch /v1/conversations/{conversation} openapi: 3.1.0 info: title: LazyApp API version: v1 description: >- One WhatsApp API for developers, SaaS platforms and businesses. Every endpoint is Bearer-authenticated with a LazyApp API key, returns JSON, and is scoped to the workspace and mode (`live` or `test`) the key belongs to. Live keys need the Pro plan. A live key on a workspace below Pro gets `402` with `code: plan_limit_reached` on every request. Test keys work on every plan, so you can build against the test number before you upgrade. LazyApp adds 0% to Meta's message rates. Meta bills each message to the business's own Meta payment method; your LazyApp plan is billed separately. contact: name: LazyApp support url: https://lazyapp.in servers: - url: https://lazyapp.in description: Production security: - bearerAuth: [] tags: - name: Messages description: Send and schedule WhatsApp messages. - name: Contacts description: The people you message, and their identifiers. - name: Conversations description: Threads and their message history. - name: Calls description: WhatsApp call history for the workspace. - name: Templates description: Create, submit and sync message templates. - name: Media description: Upload, retrieve and delete media. - name: Broadcasts description: Template sends to many contacts at once. - name: Events description: Say what happened; LazyApp picks the template. - name: Flows description: WhatsApp Flows and their responses. - name: Webhooks description: Register endpoints and inspect deliveries. - name: Workflows description: Automations and their executions. - name: Verify description: One-time passcodes over WhatsApp. - name: Capabilities description: What each connected number supports. - name: Catalog description: Proxy Meta Commerce catalog products for a connection. - name: Platform description: Manage customers if you run a platform on LazyApp. - name: Meta-compatible proxy description: Drop-in endpoints for existing Cloud API integrations. - name: Connections description: >- Your WhatsApp numbers and the account behind them: health, limits, registration, display name, blue tick, QR codes, conversation starters, opt-in links, business profile and blocked users. - name: Billing description: >- Meta's message rates, which LazyApp passes on with 0% added, and the billing facts behind them. - name: Analytics description: Workspace messaging aggregates. - name: Groups description: WhatsApp group chats on a connection Meta has enabled. - name: Funding description: Local funding status and recorded WhatsApp charges. - name: Connections description: 'WhatsApp connections: block users, business profile, insights.' - name: Payments description: >- WhatsApp payments in India: ask for payment, follow it, update the order and refund. paths: /v1/conversations/{conversation}: patch: tags: - Conversations summary: Update a conversation description: >- Assign it to a team member, set its status, replace its tags, or set the workspace-level `archived` / `pinned` flags. Only the fields you send change. Assigning starts `human_assignment` workflows, and resolving or closing starts `conversation_closed` ones, exactly as in the inbox. **Required scope:** `messages:send` parameters: - name: conversation in: path required: true schema: type: string requestBody: required: true content: application/json: schema: type: object properties: archived: type: boolean pinned: type: boolean status: type: string enum: - open - pending - resolved - closed assignee_id: type: integer nullable: true description: A member of the workspace's team, or `null` to unassign. tags: type: array maxItems: 50 items: type: string maxLength: 64 description: The conversation's whole tag set. New names are created. responses: '200': description: Updated conversation. content: application/json: schema: $ref: '#/components/schemas/Conversation' '401': description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/Error' '402': $ref: '#/components/responses/PlanLimitReached' '403': description: >- The key lacks the required scope, or is restricted from this phone number. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Not found in this workspace. content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: >- Changed in the inbox at the same moment (`conversation_changed`). Fetch it and try again. content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: Validation failed. content: application/json: schema: $ref: '#/components/schemas/ValidationError' '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: Conversation: type: object properties: id: type: string status: type: string enum: - open - pending - resolved - closed contact: type: object properties: uuid: type: string phone_number: type: string nullable: true bsuid: type: string nullable: true assignee: type: object properties: id: type: integer name: type: string nullable: true messages_count: type: integer first_message_at: type: string format: date-time nullable: true last_message_at: type: string format: date-time nullable: true last_inbound_at: type: string format: date-time nullable: true resolved_at: type: string format: date-time nullable: true created_at: type: string format: date-time nullable: true tags: type: array items: type: string archived: type: boolean pinned: type: boolean archived_at: type: string format: date-time nullable: true pinned_at: type: string format: date-time nullable: true Error: type: object properties: message: type: string description: Human-readable description of what went wrong. code: type: string description: >- Stable machine-readable reason, when the failure is one a client can branch on. required: - message ValidationError: type: object properties: message: type: string errors: type: object additionalProperties: type: array items: type: string description: Field name to list of failures. required: - message responses: PlanLimitReached: description: >- The workspace's plan does not allow this. A live key on a workspace below Pro gets this on every request, because the live API is a Pro feature. Upgrade in **Billing** to use live keys. Test keys are never limited, on any plan. `code` is always `plan_limit_reached`. Show `message` to the person: it names the plan to move to. Other plan limits use the same code in the console, but the API reports them differently today: a broadcast larger than the month's remaining Live broadcast sends is refused with `422` and the reason in `message`, and connecting a number beyond the plan's number capacity fails validation (`422`) on `phone_number_id`. content: application/json: schema: type: object properties: message: type: string description: >- A sentence you can show to the person. Says which plan to move to. code: type: string enum: - plan_limit_reached required: - message - code example: message: >- The API is on the Pro plan. Upgrade in Billing to use live keys. Test keys keep working. code: plan_limit_reached securitySchemes: bearerAuth: type: http scheme: bearer description: Your API key, e.g. `sk_live_...` or `sk_test_...`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.