ClickFunnels Orders::Applied Tag API

openapi: 3.2.0
info:
  title: ClickFunnels Orders::Applied Tag API
  termsOfService: https://www.clickfunnels.com/terms-of-service
  contact:
    name: ClickFunnels API Team
    url: https://developers.myclickfunnels.com
  x-logo:
    url: https://statics.myclickfunnels.com/image/1126065/file/31edf05760fafe41a82f16a668ab251f.png
  description: 'The ClickFunnels REST API that powers webhooks, native integrations, and Zapier lets you manage your ClickFunnels data, automate your workflows, and recreate ClickFunnels functionality in your own apps.

    '
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
  version: 2.0.0
servers:
- url: https://{subdomain}.myclickfunnels.com/api/v2
  description: ClickFunnels API
  variables:
    subdomain:
      default: myworkspace
security:
- BearerAuth: []
tags:
- name: Orders::AppliedTag
  description: '> Order Applied Tags


    The Order Applied Tags APIs allow you to list, apply and remove tags associated with a specific order.


    To utilize this, first obtain the Tag IDs for all the Order Tags for your workspace via the Orders::Tag API.


    You can manage tags for any order by creating or deleting the corresponding Applied Tags as needed.


    Note:

    There is no ''update'' method for this resource since you should just remove or add a new tag to change them.

    '
paths:
  /orders/{order_id}/applied_tags:
    get:
      tags:
      - Orders::AppliedTag
      summary: List Applied Tags
      description: List the applied tags for an order
      operationId: listOrdersAppliedTags
      parameters:
      - name: order_id
        in: path
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/after'
      - $ref: '#/components/parameters/sort_order'
      - $ref: '#/components/parameters/sort_property'
      responses:
        '200':
          description: OK
          headers:
            Pagination-Next:
              $ref: '#/components/headers/PaginationNext'
            Link:
              $ref: '#/components/headers/Link'
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/OrdersAppliedTagAttributes'
              example:
              - id: 2
                public_id: lEKehP
                order_id: 13
                tag_id: 16
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
              - id: 3
                public_id: OqpYlF
                order_id: 14
                tag_id: 18
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: API key missing or invalid
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Not found - This usually happens when you try to access a record that does not exist in your account. It can also happen when the provided parent record is missing, e.g. you have put in a non-existent Workspaces parent ID.
              example:
                error: 'Not found: Record missing'
    post:
      tags:
      - Orders::AppliedTag
      summary: Create Applied Tag
      description: Assign a tag to an order by creating an applied tag
      operationId: createOrdersAppliedTags
      parameters:
      - name: order_id
        in: path
        required: true
        schema:
          type: string
      requestBody:
        description: Information about a new Applied Tag
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                orders_applied_tag:
                  type: object
                  $ref: '#/components/schemas/OrdersAppliedTagParameters'
            example:
              orders_applied_tag:
                tag_id: 4
      responses:
        '201':
          description: Created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OrdersAppliedTagAttributes'
              example:
                id: 5
                public_id: nJDRra
                order_id: 16
                tag_id: 22
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: 'Bad request: HTTP body must be valid JSON'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: API key missing or invalid
  /orders/applied_tags/{id}:
    get:
      tags:
      - Orders::AppliedTag
      summary: Fetch Applied Tag
      description: Retrieve an applied tag for an order
      operationId: getOrdersAppliedTags
      parameters:
      - $ref: '#/components/parameters/id'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OrdersAppliedTagAttributes'
              example:
                id: 4
                public_id: HTKRAQ
                order_id: 15
                tag_id: 20
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: API key missing or invalid
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: 'Not found: Record missing'
    delete:
      tags:
      - Orders::AppliedTag
      summary: Remove Applied Tag
      description: Remove a tag from an order by deleting an applied tag
      operationId: removeOrdersAppliedTags
      parameters:
      - $ref: '#/components/parameters/id'
      responses:
        '204':
          description: No Content
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: API key missing or invalid
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: 'Not found: Record missing'
components:
  parameters:
    id:
      name: id
      in: path
      required: true
      schema:
        type: string
    sort_property:
      name: sort_property
      in: query
      description: 'Sort property of a list response. The default is id and thus the created_at order.

        If you sort by other properties, we additionally sort by id implicitly as a secondary sort property, so that you can rely on the sort order to be deterministic even if the main sort property ends up with the same values.

        '
      required: false
      schema:
        type: string
        enum:
        - id
        - updated_at
    sort_order:
      name: sort_order
      in: query
      description: Sort order of a list response. Use 'desc' to reverse the default 'asc' (ascending) sort order. Examples [in our guides](https://developers.myclickfunnels.com/docs/pagination).
      required: false
      schema:
        type: string
        enum:
        - asc
        - desc
    after:
      name: after
      in: query
      required: false
      schema:
        type: string
      description: ID of item after which the collection should be returned. More examples and info about pagination [in our guides](https://developers.myclickfunnels.com/docs/pagination).
  schemas:
    OrdersAppliedTagParameters:
      type: object
      title: Orders Applied Tags
      description: Orders Applied Tags
      required:
      - tag_id
      properties:
        tag_id:
          type: integer
          description: Tag ID
      example:
        orders_applied_tag:
          tag_id: 4
    OrdersAppliedTagAttributes:
      type: object
      title: Orders Applied Tags
      description: Orders Applied Tags
      properties:
        id:
          type: integer
          description: Applied Tag ID
        public_id:
          type:
          - string
          - 'null'
          description: Applied Tag public ID
        order_id:
          type: integer
          description: Order ID
        tag_id:
          type: integer
          description: Tag ID
        created_at:
          type:
          - string
          - 'null'
          format: date-time
          description: Date added
        updated_at:
          type:
          - string
          - 'null'
          format: date-time
          description: Last updated
      example:
        id: 1
        public_id: UZzNVm
        order_id: 3
        tag_id: 4
        created_at: '2025-01-01T00:00:00.000Z'
        updated_at: '2025-01-01T00:00:00.000Z'
      required:
      - created_at
      - id
      - order_id
      - public_id
      - tag_id
      - updated_at
  headers:
    Link:
      description: A direct link to the next page for the cursor-based pagination. It includes the `after` and the Pagination-Next ID value.
      schema:
        type: string
    PaginationNext:
      description: ID of the last item in the current response after which more records exist. You can use it in an `after` query parameter for cursor-based pagination to get to the next page.
      schema:
        type: string
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
externalDocs:
  description: More in-depth guides and further resources
  url: https://developers.myclickfunnels.com