Skip to content

HubSpot: Restore a previous version of a folder

HubSpot pages.landingPagesRestoreFolderRevision: arguments, response, policy and SDK examples.

← Pages operations · Get started

Operation hubspot.pages_landing_pages_restore_folder_revision

Provider route: POST /cms/pages/2026-09/landing-pages/folders/{objectId}/revisions/{revisionId}/restore. Alter supplies the connection’s credentials and routing.

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"]["landingPagesRestoreFolderRevision"]>[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.landingPagesRestoreFolderRevision(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from 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_restore_folder_revision(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.objectIdstringRequired within parent
path.revisionIdstringRequired within parent

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Create a landing page folder — response body

Referenced models: Create a landing page folder — response body

Create a landing page folder — response body
FieldTypePresenceDescription and constraints
$objectRoot
categoryJSONRequired within parent
category (anyOf 1)integerAlternativeThe type of object this folder applies to. Should always be LANDING_PAGE.
Format: int32
category (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
createdstringRequired within parentThe timestamp indicating when the content folder was created.
Format: date-time
deletedAtstringRequired within parentThe timestamp (ISO8601 format) when this content folder was deleted.
Format: date-time
idstringRequired within parentThe unique ID of the content folder.
namestringRequired within parentThe name of the folder which will show up in the app dashboard
parentFolderIdJSONRequired within parent
parentFolderId (anyOf 1)integerAlternativeThe ID of the content folder this folder is nested under
Format: int64
parentFolderId (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
updatedstringRequired within parentThe timestamp indicating when the content folder was last updated.
Format: date-time

SDK function policy ID: hubspot.pages_landing_pages_restore_folder_revision. Catalog operation: pages_landing_pages_restore_folder_revision. 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"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.