Please enable JavaScript to view this site.

Made in EU
HubSpot Forums

HubSpot API Data Model

Navigation: Catalog: Authors3 > Schemas

BlogAuthors: HubSpot Blog Authors

Get all Blog AuthorsGet the list of blog authors. Supports paging and filtering. This method would be useful for an integration that examined these models and used an external service to suggest edits.

Catalog: Authors3

Schema: BlogAuthors

Label: Blog Authors

Retrieve: true

Insert: true

Update: false

Delete: false

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function BlogAuthors. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

after

string

☐

 

The cursor token value to get the next set of results. You can get this from the `paging.next.after` JSON property of a paged response containing more results.

archived

boolean

☐

 

Specifies whether to return deleted Blog Authors. Defaults to `false`.

createdAfter

datetime

☐

 

Only return Blog Authors created after the specified time.

createdAt

datetime

☐

 

Only return Blog Authors created at exactly the specified time.

createdBefore

datetime

☐

 

Only return Blog Authors created before the specified time.

property

string

☐

 

 

updatedAfter

datetime

☐

 

Only return Blog Authors last updated after the specified time.

updatedAt

datetime

☐

 

Only return Blog Authors last updated at exactly the specified time.

updatedBefore

datetime

☐

 

Only return Blog Authors last updated before the specified time.

 

Columns of Table Function

The columns of the table function BlogAuthors are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert.

Name

Data Type

Label

Required

Documentation

avatar

string

Avatar

☐

URL to the blog author's avatar, if supplying a custom one.

bio

string

Biography

☐

A short biography of the blog author.

created

datetime

Created at

☐

 

deletedAt

datetime

Deleted at

☐

The timestamp (ISO8601 format) when this Blog Author was deleted.

displayName

string

Display Name

☐

The full name of the Blog Author to be displayed.

email

string

Email

☐

Email address of the Blog Author.

facebook

string

Facebook

☐

URL to the Blog Author's Facebook page.

fullName

string

Full Name

☐

 

id

string

ID

☐

The unique ID of the Blog Author.

language

string

Language

☐

The explicitly defined ISO 639 language code of the blog author.

linkedin

string

LinkedIn

☐

URL to the blog author's LinkedIn page.

name

string

Name

☐

 

slug

string

Slug

☐

 

translatedFromId

int64

Translated from ID

☐

ID of the primary blog author this object was translated from.

twitter

string

Twitter

☐

URL or username of the Twitter account associated with the Blog Author. This will be normalized into the Twitter url for said user.

updated

datetime

Updated at

☐

 

website

string

Website

☐

URL to the website of the Blog Author.

 

18-12-2024 20:09 Version 24.1.33-BETA+5180

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer