> ## Documentation Index
> Fetch the complete documentation index at: https://developers.hubspot.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
---
id: 5881453d-9104-439d-bb9f-b86dc9044e7c
---
# Retrieve a landing page folder
> Retrieve a landing page folder, specified by its ID.
export const ScopesList = ({scopes = [], description = "This API requires one of the following scopes:"}) => {
if (!scopes || scopes.length === 0) {
return null;
}
const sortedScopes = scopes.sort((a, b) => a.localeCompare(b));
return
;
};
## OpenAPI
````yaml specs/2026-03/cms-pages-v2026-03.json GET /cms/pages/2026-03/landing-pages/folders/{objectId}
openapi: 3.0.1
info:
title: Pages
description: Basepom for all HubSpot Projects
version: 2026-03
x-hubspot-product-tier-requirements:
marketing: FREE
sales: FREE
service: FREE
cms: FREE
commerce: FREE
crmHub: FREE
dataHub: FREE
x-hubspot-api-use-case: >-
After noticing that a website page was updated incorrectly, use the API to
view revisions of that page, then restore the page to a previous version.
x-hubspot-introduction: Use the pages API to create and manage website pages.
servers:
- url: https://api.hubapi.com
security: []
tags:
- name: A/B tests
- name: Advanced
- name: Basic
- name: Batch
- name: Folders
- name: Landing pages
- name: Multi-language
- name: Website pages
paths:
/cms/pages/2026-03/landing-pages/folders/{objectId}:
get:
tags:
- Folders
summary: Retrieve a landing page folder
description: Retrieve a landing page folder, specified by its ID.
operationId: get-/cms/pages/2026-03/landing-pages/folders/{objectId}_getFolderById
parameters:
- name: objectId
in: path
description: ''
required: true
style: simple
explode: false
schema:
type: string
- name: archived
in: query
description: Whether to return only results that have been archived.
required: false
style: form
explode: true
schema:
type: boolean
- name: property
in: query
description: ''
required: false
style: form
explode: true
schema:
type: string
responses:
'200':
description: successful operation
content:
application/json:
schema:
$ref: '#/components/schemas/ContentFolder'
default:
$ref: '#/components/responses/Error'
description: ''
security:
- oauth2:
- content
- oauth2:
- content.landing_pages.read
components:
schemas:
ContentFolder:
required:
- category
- created
- deletedAt
- id
- name
- parentFolderId
- updated
type: object
properties:
category:
type: integer
description: >-
The type of object this folder applies to. Should always be
LANDING_PAGE.
format: int32
created:
type: string
description: The timestamp indicating when the content folder was created.
format: date-time
deletedAt:
type: string
description: The timestamp (ISO8601 format) when this content folder was deleted.
format: date-time
id:
type: string
description: The unique ID of the content folder.
name:
type: string
description: The name of the folder which will show up in the app dashboard
parentFolderId:
type: integer
description: The ID of the content folder this folder is nested under
format: int64
updated:
type: string
description: The timestamp indicating when the content folder was last updated.
format: date-time
Error:
required:
- category
- correlationId
- message
type: object
properties:
category:
type: string
description: The error category
context:
type: object
additionalProperties:
type: array
items:
type: string
description: Context about the error condition
example: >-
{invalidPropertyName=[propertyValue], missingScopes=[scope1,
scope2]}
correlationId:
type: string
description: >-
A unique identifier for the request. Include this value with any
error reports or support tickets
format: uuid
example: aeb5f871-7f07-4993-9211-075dc63e7cbf
errors:
type: array
description: further information about the error
items:
$ref: '#/components/schemas/ErrorDetail'
links:
type: object
additionalProperties:
type: string
description: >-
A map of link names to associated URIs containing documentation
about the error or recommended remediation steps
message:
type: string
description: >-
A human readable message describing the error along with remediation
steps where appropriate
example: An error occurred
subCategory:
type: string
description: >-
A specific category that contains more specific detail about the
error
description: >-
Represents an error response returned by the API when an operation
fails. This component is used in various endpoints to provide detailed
information about the error encountered.
example:
message: Invalid input (details will vary based on the error)
correlationId: aeb5f871-7f07-4993-9211-075dc63e7cbf
category: VALIDATION_ERROR
links:
knowledge-base: https://www.hubspot.com/products/service/knowledge-base
ErrorDetail:
required:
- message
type: object
properties:
code:
type: string
description: The status code associated with the error detail
context:
type: object
additionalProperties:
type: array
items:
type: string
description: Context about the error condition
example: '{missingScopes=[scope1, scope2]}'
in:
type: string
description: The name of the field or parameter in which the error was found.
message:
type: string
description: >-
A human readable message describing the error along with remediation
steps where appropriate
subCategory:
type: string
description: >-
A specific category that contains more specific detail about the
error
description: >-
Represents detailed information about an error that occurred in the API.
This component is used to provide additional context and specifics about
errors, typically as part of an error response.
responses:
Error:
description: An error occurred.
content:
'*/*':
schema:
$ref: '#/components/schemas/Error'
securitySchemes:
oauth2:
type: oauth2
flows:
authorizationCode:
authorizationUrl: https://app.hubspot.com/oauth/authorize
tokenUrl: https://api.hubapi.com/oauth/v1/token
scopes:
content: ''
content.landing_pages.read: ''
sitepages-read: ''
````
{product.name} -
{product.level}
)}