ClickFunnels

ClickFunnels Contacts::Applied Tag API

> Contact Applied Tags The Contact Applied Tags APIs allow you to list, apply and remove tags associated with a specific contact. To utilize this, first obtain the Tag IDs for all the Contact Tags for your workspace via the Contacts::Tags API. You can manage tags for any contact by creating or deleting the corresponding Applied Tags as needed. Note: There is no 'update' method for this API since you should just remove and add a new tag to change them.

GitHub OpenAPI

Operations 4

GET /contacts/{contact_id}/applied_tags List Applied Tags #
POST /contacts/{contact_id}/applied_tags Create Applied Tag #
GET /contacts/applied_tags/{id} Fetch Applied Tag #
DELETE /contacts/applied_tags/{id} Remove Applied Tag #

Documentation

📖
Documentation
https://developers.myclickfunnels.com/docs/intro
📖
APIReference
https://developers.myclickfunnels.com/reference
📖
GettingStarted
https://developers.myclickfunnels.com/docs/getting-started
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/clickfunnels/refs/heads/main/rate-limits/clickfunnels-rate-limits.yml

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/clickfunnels/refs/heads/main/openapi/clickfunnels-contacts-appliedtag-api-openapi.yml

Other Resources

🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/clickfunnels/refs/heads/main/data-model/clickfunnels-data-model.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/clickfunnels/refs/heads/main/errors/clickfunnels-problem-types.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/clickfunnels-contacts-appliedtag-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

clickfunnels-contacts-appliedtag-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: ClickFunnels Contacts::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: Contacts::AppliedTag
  description: '> Contact Applied Tags


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


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


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


    Note:

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

    '
paths:
  /contacts/{contact_id}/applied_tags:
    get:
      tags:
      - Contacts::AppliedTag
      summary: List Applied Tags
      description: List the applied tags for a contact
      operationId: listContactsAppliedTags
      parameters:
      - name: contact_id
        in: path
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/after'
      - $ref: '#/components/parameters/sort_order'
      - $ref: '#/components/parameters/sort_property'
      - name: filter
        in: query
        description: 'Filter by available properties in query params, like this: `api/v2/resources?filter[id]=value&filter[another_property]=value1,value2`. Check our Filtering guide for examples and all about filtering [here](https://developers.myclickfunnels.com/docs/filtering).

          '
        required: false
        schema:
          type: object
          properties:
            id:
              type: string
              description: A comma-separated list of applied tag IDs to filter by.
              example: 1,42
            tag_id:
              type: string
              description: A comma-separated list of tag IDs to filter by.
              example: 1,2,3
        style: deepObject
        explode: true
      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/ContactsAppliedTagAttributes'
              example:
              - id: 2
                public_id: AYevzG
                contact_id: 1
                tag_id: 51
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
                tag:
                  public_id: QeOyXv
                  name: Example Tag
                  color: '#00FF00'
                contact:
                  id: 24359
                  public_id: vQxYMj
                  email_address: jane.doe@example.com
                  first_name: Jane
                  last_name: Doe
                  phone_number: '+18005550199'
              - id: 3
                public_id: hIQuPR
                contact_id: 1
                tag_id: 52
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
                tag:
                  public_id: wjGBNe
                  name: Example Tag
                  color: '#00FF00'
                contact:
                  id: 24359
                  public_id: vQxYMj
                  email_address: jane.doe@example.com
                  first_name: Jane
                  last_name: Doe
                  phone_number: '+18005550199'
        '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:
      - Contacts::AppliedTag
      summary: Create Applied Tag
      description: Assign a tag to a contact by creating an applied tag
      operationId: createContactsAppliedTags
      parameters:
      - name: contact_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:
                contacts_applied_tag:
                  type: object
                  $ref: '#/components/schemas/ContactsAppliedTagParameters'
            example:
              contacts_applied_tag:
                tag_id: 3
      responses:
        '201':
          description: Created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ContactsAppliedTagAttributes'
              example:
                id: 5
                public_id: jgqvTJ
                contact_id: 1
                tag_id: 54
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
                tag:
                  public_id: wvVYaj
                  name: Example Tag
                  color: '#00FF00'
                contact:
                  id: 24359
                  public_id: vQxYMj
                  email_address: jane.doe@example.com
                  first_name: Jane
                  last_name: Doe
                  phone_number: '+18005550199'
        '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
  /contacts/applied_tags/{id}:
    get:
      tags:
      - Contacts::AppliedTag
      summary: Fetch Applied Tag
      description: Retrieve an applied tag for a contact
      operationId: getContactsAppliedTags
      parameters:
      - $ref: '#/components/parameters/id'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ContactsAppliedTagAttributes'
              example:
                id: 4
                public_id: VNCLKs
                contact_id: 1
                tag_id: 53
                created_at: '2025-01-01T00:00:00.000Z'
                updated_at: '2025-01-01T00:00:00.000Z'
                tag:
                  public_id: ovwMke
                  name: Example Tag
                  color: '#00FF00'
                contact:
                  id: 24359
                  public_id: vQxYMj
                  email_address: jane.doe@example.com
                  first_name: Jane
                  last_name: Doe
                  phone_number: '+18005550199'
        '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:
      - Contacts::AppliedTag
      summary: Remove Applied Tag
      description: Remove a tag from a contact by deleting an applied tag
      operationId: removeContactsAppliedTags
      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:
  schemas:
    ContactsAppliedTagAttributes:
      type: object
      title: Contacts Applied Tags
      description: Contacts Applied Tags
      properties:
        id:
          type: integer
          description: Applied Tag ID
        public_id:
          type:
          - string
          - 'null'
          description: Applied Tag public ID
        contact_id:
          type: integer
          description: Contact 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
        tag:
          type: object
          title: Contact Tags
          description: Contact Tags
          properties:
            public_id:
              type:
              - string
              - 'null'
              description: Tag public ID
            name:
              type: string
              description: Name
            color:
              type: string
              description: Color
        contact:
          $ref: '#/components/schemas/ContactShortAttributes'
      example:
        id: 1
        public_id: PYfeiE
        contact_id: 1
        tag_id: 3
        created_at: '2025-01-01T00:00:00.000Z'
        updated_at: '2025-01-01T00:00:00.000Z'
        tag:
          public_id: KekAvg
          name: Example Tag
          color: '#00FF00'
        contact:
          id: 24359
          public_id: vQxYMj
          email_address: jane.doe@example.com
          first_name: Jane
          last_name: Doe
          phone_number: '+18005550199'
      required:
      - contact
      - contact_id
      - created_at
      - id
      - public_id
      - tag
      - tag_id
      - updated_at
    ContactsAppliedTagParameters:
      type: object
      title: Contacts Applied Tags
      description: Contacts Applied Tags
      required:
      - tag_id
      properties:
        tag_id:
          type: integer
          description: Tag ID
      example:
        contacts_applied_tag:
          tag_id: 3
    ContactShortAttributes:
      type: object
      title: Contact (Short)
      description: A compact contact representation used in nested resources.
      properties:
        id:
          type: integer
          description: The ID of the contact.
        public_id:
          type: string
          description: The public ID of the contact.
        email_address:
          type: string
          description: The email address of the contact.
        first_name:
          type:
          - string
          - 'null'
          description: The first name of the contact.
        last_name:
          type:
          - string
          - 'null'
          description: The last name of the contact.
        phone_number:
          type:
          - string
          - 'null'
          description: The phone number of the contact.
      example:
        id: 24359
        public_id: vQxYMj
        email_address: jane.doe@example.com
        first_name: Jane
        last_name: Doe
        phone_number: '+18005550199'
      required:
      - email_address
      - first_name
      - id
      - last_name
      - phone_number
      - public_id
  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).
  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