curl --request GET \
--url https://api.hubapi.com/marketing/v3/campaigns/{campaignGuid}/assets/{assetType} \
--header 'Authorization: Bearer <token>'{
"results": [
{
"id": "<string>",
"metrics": {},
"name": "<string>"
}
],
"paging": {
"next": {
"after": "<string>",
"link": "<string>"
}
}
}This endpoint lists all assets of the campaign by asset type. The assetType parameter is required, and each request can only fetch assets of a single type. Asset metrics can also be fetched along with the assets; they are available only if start and end dates are provided.
curl --request GET \
--url https://api.hubapi.com/marketing/v3/campaigns/{campaignGuid}/assets/{assetType} \
--header 'Authorization: Bearer <token>'{
"results": [
{
"id": "<string>",
"metrics": {},
"name": "<string>"
}
],
"paging": {
"next": {
"after": "<string>",
"link": "<string>"
}
}
}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.
Supported products
Required Scopes
The access token received from the authorization server in the OAuth 2.0 flow.
The type of asset to associate with the campaign. Required. Example: BLOG_POST.
The UUID of the campaign, required Example: 9dbec438-53e2-4b28-8c0f-38f56574a6e8
The paging cursor token of the last successfully read resource will be returned as the paging.next.after JSON property of a paged response containing more results.
The end date for fetching asset metrics, in YYYY-MM-DD format.
Optional. Example: 2000-01-27
The maximum number of results to display per page.
The start date for fetching asset metrics, in YYYY-MM-DD format.
Optional. Example: 2000-01-20
Was this page helpful?