Find CMS blocks

Prev Next
Post
/cmsBlocks/find

Returns one page as a plain array, without a total count. Use get for the full block. All body fields are optional; send an empty body or {} to get the first page of active blocks. Text filters are case-insensitive substring matches and are combined with AND. Text filters also apply to forms listed as blocks.

Body fields:

  • lifecycleStatus: lifecycle statuses to include, ACTIVE and/or ARCHIVED. Defaults to ACTIVE.
  • contentTypes: content types to include: EMAIL, FORM, IN_APP, MICROSITE. FORM includes forms listed as blocks. Defaults to all content types.
  • page: zero-based page number. Defaults to 0.
  • size: results per page. Defaults to 25; values above 100 are capped at 100.
  • name: matches the block name.
  • author: matches the creator's full name (first name, a space, then last name).
  • assignedTo: matches the assignee's full name (first name, a space, then last name).
  • created / modified: matches the creation / last modification time in yyyy-MM-dd HH:mm:ss format, e.g. 2026-11 or 2026-11-04.
Body parameters

Optional filter and paging criteria. See the operation notes for the fields.

object
lifecycleStatus
Array of string
string
Valid values[ "ACTIVE", "ARCHIVED" ]
contentTypes
Array of string
string
Valid values[ "EMAIL", "FORM", "IN_APP", "MICROSITE" ]
page
integer (int32)
size
integer (int32)
name
string
author
string
assignedTo
string
created
string
modified
string
Responses
200

The blocks on the requested page.

Example response:

[
  {
    "id": 9405,
    "name": "Welcome text",
    "tags": "welcome,onboarding",
    "lifecycleStatus": "ACTIVE",
    "folder": "Onboarding",
    "status": "WORKINPROGRESS",
    "createDate": 1792998000000,
    "modifyDate": 1793001600000
  }
]
Array of object
object
id
integer (int64)
name
string
tags
string
lifecycleStatus
string
Valid values[ "ACTIVE", "ARCHIVED" ]
folder
string
status
string
Valid values[ "FINISHED", "WORKINPROGRESS" ]
createDate
integer (int64)
modifyDate
integer (int64)
400

Error. All errors are returned as HTTP 400; errorCode in the body says what went wrong: INVALID_PARAMETER or MISSING_PARAMETER (a parameter is missing or invalid), NO_SUCH_OBJECT (no object with this ID in your account), PERMISSION_DENIED (your user lacks the CMS permission for this action), UNEXPECTED_ERROR (backend error). Example: {"errorActor": "CLIENT", "errorCode": "NO_SUCH_OBJECT", "message": "...", "objectType": null, "propertyName": null, "propertyValue": null}