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

# Delete brief

> Deletes a brief. Requires permission `delete/brief`.
Any role other than the owner gets 404 for a brief that is not shared with their role.
The brief moves to **Settings › Trash** and disappears from the web and mobile lists at once. The stored PDF is kept.



## OpenAPI

````yaml /openapi/public/openapi-flow.json delete /brief/{id}
openapi: 3.0.0
info:
  title: API - Flow
  version: 3.0.0
  description: API Documentation - RESTful API for field operations management.
servers:
  - url: https://apiweb.mile.app/api/v3
security:
  - bearerAuth: []
tags:
  - name: Flow
    description: >-
      Flow is the mobile field application workflow, setting it correctly is
      critical to the success of the field workers in doing their job
      efficiently. Flow attributes consist of IDs, pages, components,
      configurations, and time. The Flow will be used at Task, Automation, or
      Schedule.


      **To see the details of flow object, please follow [this
      link](#tag/flow_model)**
  - name: Automation
    description: >-
      Automation enables you to set up automation based on tasks' events and
      data source's events. It might help you automate creation of tasks, task
      assignment, task placement, task webhook, data source update, datasource
      creation, and data source webhook. Automation attributes consist of IDs,
      automation name, automation type, automation details, and rules.


      **To see the details of automation object, please follow [this
      link](#tag/automation_model)**
  - name: Order Type
    description: >-
      An order type is the blueprint for orders: the list of steps, which flow
      each step uses, and how an order moves from one step to the next. Order
      types are versioned: you edit a draft, validate or simulate it, then
      publish it. These endpoints are served under `/api/v4`.
  - name: Brief
    description: >-
      A brief is a reference PDF, such as an SOP, a product guide or a campaign
      brief, that your field team reads in the mobile app. It comes from an
      https link or an uploaded PDF, and it is shared with chosen roles or with
      every role. These endpoints are served under `/api/v4`.
paths:
  /brief/{id}:
    servers:
      - url: https://apiweb.mile.app/api/v4
    delete:
      tags:
        - Brief
      summary: Delete brief
      description: >-
        Deletes a brief. Requires permission `delete/brief`.

        Any role other than the owner gets 404 for a brief that is not shared
        with their role.

        The brief moves to **Settings › Trash** and disappears from the web and
        mobile lists at once. The stored PDF is kept.
      operationId: deleteBrief
      parameters:
        - name: id
          in: path
          required: true
          description: |-
            Unique identifier for the brief that generated by system.
            **Example**: `6738a1f2c4e9b10012ab34cd`
          schema:
            type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: boolean
                    description: Status of response.
                  message:
                    description: Message of API response.
                    type: string
                  data:
                    description: Always null.
                    type: object
                    additionalProperties: true
                example:
                  status: true
                  message: Success.
                  data: null
        '404':
          description: Data not found
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: boolean
                    description: Status of response.
                  message:
                    description: Message of API response.
                    type: string
                  data:
                    description: Always null on error.
                    type: object
                    additionalProperties: true
                  failedCode:
                    description: Error code, see the descriptions above.
                    type: string
                example:
                  status: false
                  message: >-
                    Data not found. Please check the ID or reference number and
                    try again.
                  data: null
                  failedCode: brief-033
        '500':
          description: Server error
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: boolean
                    description: Shows if the request was successful.
                  message:
                    type: string
                    description: A short message explaining what went wrong.
                example:
                  status: false
                  message: Internal server error, please contact support@mile.app.
      deprecated: false
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Use a valid Bearer token to authenticate.

````

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