openapi: 3.2.0 info: title: ClickFunnels Forms::Field Set 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: Forms::FieldSet description: Form FieldSets paths: /forms/{form_id}/field_sets: get: tags: - Forms::FieldSet summary: List Field Sets description: List field sets for a form operationId: listFormsFieldSets parameters: - name: form_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/FormsFieldSetAttributes' example: - id: 142 public_id: uOqvKD form_id: 153 title: Example Field Set created_at: '2025-01-01T00:00:00.000Z' updated_at: '2025-01-01T00:00:00.000Z' - id: 143 public_id: OlXgZI form_id: 154 title: Example Field Set 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: - Forms::FieldSet summary: Create Field Set description: Add a new field set operationId: createFormsFieldSets parameters: - name: form_id in: path required: true schema: type: string requestBody: description: Information about a new Field Set required: true content: application/json: schema: type: object properties: forms_field_set: type: object $ref: '#/components/schemas/FormsFieldSetParameters' example: forms_field_set: title: Example Field Set responses: '201': description: Created content: application/json: schema: $ref: '#/components/schemas/FormsFieldSetAttributes' example: id: 145 public_id: arSZpR form_id: 156 title: Example Field Set 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 /forms/field_sets/{id}: get: tags: - Forms::FieldSet summary: Fetch Field Set description: Retrieve a field set operationId: getFormsFieldSets parameters: - $ref: '#/components/parameters/id' responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/FormsFieldSetAttributes' example: id: 144 public_id: JktQra form_id: 155 title: Example Field Set 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' put: tags: - Forms::FieldSet summary: Update Field Set description: Update a field set operationId: updateFormsFieldSets parameters: - $ref: '#/components/parameters/id' requestBody: description: Information about updated fields in Field Set required: true content: application/json: schema: type: object properties: forms_field_set: type: object $ref: '#/components/schemas/FormsFieldSetParametersUpdate' example: forms_field_set: title: Example Field Set responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/FormsFieldSetAttributes' example: id: 147 public_id: hYMOjn form_id: 158 title: Example Field Set 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 '404': description: Not Found content: application/json: schema: type: object properties: error: type: string example: error: 'Not found: Record missing' delete: tags: - Forms::FieldSet summary: Remove Field Set description: Delete a field set operationId: removeFormsFieldSets 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: FormsFieldSetAttributes: type: object title: Field sets description: Field sets properties: id: type: integer description: Field set ID public_id: type: - string - 'null' description: Field set public ID form_id: type: integer description: Form ID title: type: string description: Title created_at: type: - string - 'null' format: date-time description: Added updated_at: type: - string - 'null' format: date-time description: Updated example: id: 9 public_id: wzITqe form_id: 10 title: Example Field Set created_at: '2025-01-01T00:00:00.000Z' updated_at: '2025-01-01T00:00:00.000Z' required: - created_at - form_id - id - public_id - title - updated_at FormsFieldSetParameters: type: object title: Field sets description: Field sets required: - title properties: title: type: string description: Title example: forms_field_set: title: Example Field Set FormsFieldSetParametersUpdate: type: object title: Field sets description: Field sets required: [] properties: title: type: string description: Title example: forms_field_set: title: Example Field Set 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