# Hubspot Knowledge Base API

**URL:** <https://community.hubspot.com/t/hubspot-knowledge-base-api/10457>\
**Category:** HubSpot Ideas\
**Tags:** integrations\
**Created:** [October 3, 2018, 4:50pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457 "2018-10-03T16:50:08Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![rw1982](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rw1982/32/95715_2.png) [@rw1982](https://community.hubspot.com/u/rw1982)\
**Post date:** [March 11, 2025, 1:18pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/41 "2025-03-11T13:18:14Z")

</div>

No news yet? 🙂

---

<div class="post-metadata">

**Author:** ![MikaelFurst](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mikaelfurst/32/41549_2.png) [@MikaelFurst](https://community.hubspot.com/u/MikaelFurst)\
**Post date:** [April 24, 2025, 11:36am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/42 "2025-04-24T11:36:59Z")

</div>

Have there really been no updates on the Knowledge Base API? Five years is quite a long time, especially considering how frequently it’s been requested.

---

<div class="post-metadata">

**Author:** ![mffap](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@mffap](https://community.hubspot.com/u/mffap)\
**Post date:** [May 14, 2025, 11:37am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/43 "2025-05-14T11:37:15Z")

</div>

This is really required for us to move content over. The KB can’t be customized so it makes sense within our website, we want to pull just the content and handle display ourselves while using KB content for support flows in Service Hub.

---

<div class="post-metadata">

**Author:** ![ClaireBIGENIUS](https://avatars.discourse-cdn.com/v4/letter/c/59ef9b/32.png) [@ClaireBIGENIUS](https://community.hubspot.com/u/ClaireBIGENIUS)\
**Post date:** [May 14, 2025, 4:19pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/44 "2025-05-14T16:19:56Z")

</div>

+1 how is it possible that we can access everything except the knowledge base with the hubspot API!

---

<div class="post-metadata">

**Author:** ![MarcoHuber](https://avatars.discourse-cdn.com/v4/letter/m/7ea924/32.png) [@MarcoHuber](https://community.hubspot.com/u/MarcoHuber)\
**Post date:** [July 4, 2025, 10:58am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/45 "2025-07-04T10:58:18Z")

</div>

**Guys, seriously?**

Your last official statement on this was in 2020, acknowledging it’s a relevant topic. Since then—_nothing_.  
This idea now has over **200 upvotes** and clearly addresses a **critical need** for many users.

Please re-evaluate your priorities.

This isn’t just a nice-to-have—it’s essential functionality that your users have been requesting for years.

---

<div class="post-metadata">

**Author:** ![PHadfield](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@PHadfield](https://community.hubspot.com/u/PHadfield)\
**Post date:** [August 8, 2025, 12:29pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/46 "2025-08-08T12:29:40Z")

</div>

One vote here

---

<div class="post-metadata">

**Author:** ![AlexHub](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@AlexHub](https://community.hubspot.com/u/AlexHub)\
**Post date:** [October 13, 2025, 6:20am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/47 "2025-10-13T06:20:00Z")

</div>

This is very critical as we don’t want to make the content public but we can’t use the widget to show private content by SSO due to this bug…

---

<div class="post-metadata">

**Author:** ![TGrosser](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@TGrosser](https://community.hubspot.com/u/TGrosser)\
**Post date:** [December 2, 2025, 1:51pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/48 "2025-12-02T13:51:48Z")

</div>

Just putting this here, because I haven’t found it immediately, and these posts are still unresponded to:  
You **can** , at least, read the entire Knowledge Base using the HubSpot GraphQL tool:

```lia-code-sample
# ---------- GraphQL Queries ----------

LIST_ARTICLES_QUERY = """
query PublishedKBArticlesNewestFirst($limit: Int!, $offset: Int!) {
 KB {
 knowledge_article_collection(
 limit: $limit
 offset: $offset
 filter: { hs_published_at__null: false }
 orderBy: [hs_published_at__desc]
 ) {
 items {
 hs_id
 hs_name
 hs_path
 hs_published_at
 }
 }
 }
}
"""

ARTICLE_DETAIL_QUERY = """
query ArticleForExport($id: String!) {
 KB {
 knowledge_article(uniqueIdentifier: "hs_id", uniqueIdentifierValue: $id) {
 id: hs_id
 title: hs_name
 subtitle: hs_summary
 path: hs_path
 lang: hs_language
 raw_format: hs_body
 published_at: hs_published_at
 updated_at: hs_updated_at
 }
 knowledge_base_collection(limit: 1, offset: 0) {
 items {
 source: hs_name
 domain: hs_domain
 kb_path: hs_slug
 }
 }
 }
}
"""

```

May not solve everyone’s problem, but solved mine.

---

<div class="post-metadata">

**Author:** ![TamF](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@TamF](https://community.hubspot.com/u/TamF)\
**Post date:** [January 26, 2026, 5:42pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/49 "2026-01-26T17:42:45Z")

</div>

Adding a comment here for a Knowledge Base API. My team just started using HubSpot and we’d assumed this was already part of the API.

Our intention was to mass create KB articles from our existing customer success content (looms, emails etc) and have Claude etc review them for consistency, style, etc and then upload them all via the API.

It would speed us up massively if we could mass submit (or edit) KB articles.

Given this thread has been open for years now, I’m not confident this is going to get done any time soon. But my vote and comment have been cast!

---

<div class="post-metadata">

**Author:** ![AnkitRawat](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ankitrawat/32/73578_2.png) [@AnkitRawat](https://community.hubspot.com/u/AnkitRawat)\
**Post date:** [March 13, 2026, 8:19am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/50 "2026-03-13T08:19:08Z")

</div>

+1 For the knowledge base API. It’s been so many years

---

<div class="post-metadata">

**Author:** ![BTanguay](https://avatars.discourse-cdn.com/v4/letter/b/e19adc/32.png) [@BTanguay](https://community.hubspot.com/u/BTanguay)\
**Post date:** [March 19, 2026, 6:31pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/51 "2026-03-19T18:31:23Z")

</div>

+1 to this  
Really need access via API to be more efficient in our development process.

---

<div class="post-metadata">

**Author:** ![NDuel](https://avatars.discourse-cdn.com/v4/letter/n/c67d28/32.png) [@NDuel](https://community.hubspot.com/u/NDuel)\
**Post date:** [May 19, 2026, 3:33am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/52 "2026-05-19T03:33:29Z")

</div>

+1 on this. In 2026, with MCPs and all the tooling now available, having no way to programmatically update articles is genuinely pushing us to look at alternatives.

---

<div class="post-metadata">

**Author:** ![JHanington](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@JHanington](https://community.hubspot.com/u/JHanington)\
**Post date:** [May 19, 2026, 3:39pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/53 "2026-05-19T15:39:49Z")

</div>

[https://community.hubspot.com/t5/HubSpot-Ideas/Hubspot-Knowledge-Base-API/idc-p/1230285/highlight/true#M222278](https://community.hubspot.com/t5/HubSpot-Ideas/Hubspot-Knowledge-Base-API/idc-p/1230285/highlight/true#M222278)  
TGrosser, thank you for providing a solution for us!

---

<div class="post-metadata">

**Author:** ![r3mpag3](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@r3mpag3](https://community.hubspot.com/u/r3mpag3)\
**Post date:** [June 30, 2026, 2:26pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/54 "2026-06-30T14:26:33Z")

</div>

2020: “not currently planned.” 2026: “being planned.” Filed five years ago, now sitting pretty on the H1 2026 roadmap as Service Hub’s “Scale Knowledge Base Management.” At this rate “in development” lands around 2032.

Genuinely curious what the gap is between “on the roadmap” and “actually shippable” — asking as an Enterprise customer who’d happily be an early tester the moment this moves one column to the left.

---

<div class="post-metadata">

**Author:** ![JPSB](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@JPSB](https://community.hubspot.com/u/JPSB)\
**Post date:** [July 9, 2026, 6:12pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/55 "2026-07-09T18:12:18Z")

</div>

Just realized there’s no API or MCP here. Super surprising. We’re now looking at moving our support docs off of Hubspot to something like Mintlify for native / agent support.

---

<div class="post-metadata">

**Author:** ![JPSB](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@JPSB](https://community.hubspot.com/u/JPSB)\
**Post date:** [July 9, 2026, 6:18pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/56 "2026-07-09T18:18:15Z")

</div>

Same. Actively migrating all of our support articles now and making it a part of our product build process using MCP / API (e.g. via Mintlify or other API first tools)

---

<div class="post-metadata">

**Author:** ![amberbachlani](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/amberbachlani/32/17188_2.png) [@amberbachlani](https://community.hubspot.com/u/amberbachlani)\
**Post date:** [July 21, 2026, 3:14pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/57 "2026-07-21T15:14:42Z")

</div>

Hello, quick update here! KB API endpoints are currently in development, and we hope to deliver in mid-Q3.

---

<div class="post-metadata">

**Author:** ![MichielJacobi](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@MichielJacobi](https://community.hubspot.com/u/MichielJacobi)\
**Post date:** [July 22, 2026, 1:54pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/58 "2026-07-22T13:54:36Z")

</div>

I need this function to be able to push content to the knowledge base - we can use a coupling to have our engineers write content for manuals on Notion and couple this through metadata and an app in between to hubspot articles.

---

<div class="post-metadata">

**Author:** ![Daandriks](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@Daandriks](https://community.hubspot.com/u/Daandriks)\
**Post date:** [September 7, 2026, 9:43am UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/59 "2026-09-07T09:43:06Z")

</div>

Awesome this is in development. @amberbachlani is there any new information available about a possible release date for the API for the Knowledge Base and will the API also work for the MCP Server?

---

<div class="post-metadata">

**Author:** ![canove](https://avatars.discourse-cdn.com/v4/letter/c/5f9b8f/32.png) [@canove](https://community.hubspot.com/u/canove)\
**Post date:** [September 22, 2026, 7:38pm UTC](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457/60 "2026-09-22T19:38:13Z")

</div>

Confirmed for this quarter?

[Previous page](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457.md?page=2)

[Next page](https://community.hubspot.com/t/hubspot-knowledge-base-api/10457.md?page=4)