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

# Resume an item

> Resume a paused or parked item at the step it stopped on.


## OpenAPI

```yaml openapi.json post /v1/companies/{campus}/items/{id}/resume
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.4.0
servers:
  - url: https://api.plungeai.com
paths:
  /v1/companies/{campus}/items/{id}/resume:
    post:
      operationId: post-v1-companies-campus-items-id-resume
      tags:
        - Companies
      summary: Resume an item
      description: Resumes a paused or parked item at the step it stopped on (a parked item starts a fresh visit). Answers the item as it is now.
      security:
        - ozkBearer: []
      parameters:
        - name: campus
          in: path
          required: true
          schema:
            type: string
          description: The company’s slug (`plunge`), never a row id
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Item id
        - name: format
          in: query
          schema:
            type: string
            enum:
              - json
              - yaml
              - markdown
              - text
          description: Response format; overrides Accept (an unknown value is 400 invalid_format)
      responses:
        "200":
          description: The item Response format negotiates via the `format` field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
          content:
            application/json:
              schema:
                type: object
                properties:
                  id:
                    type: string
                  campus:
                    type: string
                  building:
                    type: string
                  title:
                    type: string
                  body:
                    type: string
                  kind:
                    type: string
                    enum:
                      - feature
                      - bugfix
                      - docs
                      - research
                      - content
                      - task
                  source:
                    type: string
                    enum:
                      - api
                      - bot
                      - schedule
                      - then
                      - node
                  priority:
                    type: integer
                  tier:
                    type:
                      - string
                      - "null"
                    description: The standard’s tier word (`T2`, `V1`); null until set
                  step:
                    type: string
                    description: "`intake`, a step id of the building’s pipeline, `done` or `parked`"
                  attempt:
                    type: integer
                  status:
                    type: string
                    enum:
                      - active
                      - done
                      - failed
                      - parked
                  parked_reason:
                    type:
                      - string
                      - "null"
                  paused:
                    type: integer
                    enum:
                      - 0
                      - 1
                  steer:
                    type:
                      - string
                      - "null"
                  last_output:
                    type:
                      - string
                      - "null"
                    description: The previous step’s output, the next office’s `{input}`
                  cost_usd:
                    type: number
                  parent_item_id:
                    type:
                      - string
                      - "null"
                  created_at:
                    type: string
                  updated_at:
                    type: string
            text/yaml:
              schema:
                type: string
            text/markdown:
              schema:
                type: string
            text/plain:
              schema:
                type: string
        "400":
          description: invalid_json — body is not valid JSON or YAML; invalid_format — format must be one of json, yaml, markdown, text
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "401":
          description: unauthorized — missing, invalid or revoked ozk_ key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "404":
          description: "company_not_found — no company with that slug for this account (a foreign slug answers the same); or no item with that id in this company; not_found — no route for this method on this path: every other method answers it"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "409":
          description: the item is in a state this action does not apply to (the code and message say why); nothing changed
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "502":
          description: upstream_error — the company service is unavailable; retry
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "503":
          description: not_enabled — the company service is not deployed on this tier
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    Error:
      type: object
      description: Standard error envelope. Every error response also carries an `X-Error-Code` response header equal to error.code, so a client branches on the header regardless of the negotiated body format (json | yaml | markdown | text). When the request created an execution, the `X-Execution-Id` response header is also set. Errors follow the negotiated format like success bodies.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            connect:
              type: object
              description: "On a 424 connection_required / credential_required: where the missing connection is made."
              properties:
                provider:
                  type: string
                method:
                  type: string
                  enum:
                    - oauth
                    - api_key
                    - wallet
                link:
                  type: string
                  example: POST /v1/connections/stripe/link
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
```