HubSpot: Get all landing page folders
HubSpot pages.landingPagesGetFolders: arguments, response, policy and SDK examples.
← Pages operations · Get started
Operation hubspot.pages_landing_pages_get_folders
Provider route: GET /cms/pages/2026-09/landing-pages/folders. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/hubspot with npm, or alter-sdk-hubspot with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { HubSpotIntegration } from "@alter-ai/hubspot";
async function execute(input: Parameters<HubSpotIntegration["pages"]["landingPagesGetFolders"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new HubSpotIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.pages.landingPagesGetFolders(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_hubspot import HubSpotIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = HubSpotIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.pages.landing_pages_get_folders(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
query | Model | Optional | Expand List tags — request body — query |
Referenced models: List tags — request body — query
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Get all landing page folders — response body |
Referenced models: Get all landing page folders — response body
Schemas
Section titled “Schemas”Get all landing page folders — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
paging | Model | Optional | Expand Get all landing pages — response body — paging |
results | array | Required within parent | Collection of content folders. |
results[] | Model | Each item | Expand Create a landing page folder — response body |
total | JSON | Required within parent | |
total (anyOf 1) | integer | Alternative | Total number of content folders. Format: int32 |
total (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
Referenced models: Create a landing page folder — response body, Get all landing pages — response body — paging
List tags — request body — query
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
after | string | Optional | |
archived | boolean | Optional | |
createdAfter | string | Optional | Format: date-time |
createdAt | string | Optional | Format: date-time |
createdBefore | string | Optional | Format: date-time |
limit | integer | Optional | Format: int32 |
property | string | Optional | |
sort | array | Optional | |
sort[] | string | Each item | |
updatedAfter | string | Optional | Format: date-time |
updatedAt | string | Optional | Format: date-time |
updatedBefore | string | Optional | Format: date-time |
Create a landing page folder — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
category | JSON | Required within parent | |
category (anyOf 1) | integer | Alternative | The type of object this folder applies to. Should always be LANDING_PAGE. Format: int32 |
category (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
created | string | Required within parent | The timestamp indicating when the content folder was created. Format: date-time |
deletedAt | string | Required within parent | The timestamp (ISO8601 format) when this content folder was deleted. Format: date-time |
id | string | Required within parent | The unique ID of the content folder. |
name | string | Required within parent | The name of the folder which will show up in the app dashboard |
parentFolderId | JSON | Required within parent | |
parentFolderId (anyOf 1) | integer | Alternative | The ID of the content folder this folder is nested under Format: int64 |
parentFolderId (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
updated | string | Required within parent | The timestamp indicating when the content folder was last updated. Format: date-time |
Get all landing pages — response body — paging
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Paging information for forward-only pagination. Contains the next page reference when more results are available; omitted or empty on the last page. |
next | Model | Optional | Expand Get all landing pages — response body — paging next |
Referenced models: Get all landing pages — response body — paging next
Get all landing pages — response body — paging next
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Specifies the paging information needed to retrieve the next set of results in a paginated API response |
after | string | Required within parent | A string that serves as the paging cursor token, indicating the position after the last successfully read resource. It is used to fetch the next set of results in a paginated response. |
link | string | Optional | A string containing the URL link to the next page of results in a paginated response. |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: hubspot.pages_landing_pages_get_folders. Catalog operation: pages_landing_pages_get_folders. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["content"]