Get Article
Fetches one article by ID for editing, including drafts and internal articles. Returns null rather than 404 when nothing matches. Use Get Public Article for the reader-facing lookup, which is by slug and only returns published content.
Authorization
Authorization In: header
Path Parameters
ID of the project that owns the article.
ID of the article to fetch.
Query Parameters
Only return the article if it belongs to this help center. Omit to search the whole project.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://www.saasco.com/api/v2/projects/string/knowledge/articles/string"{
"id": "string",
"createdAt": "string",
"updatedAt": "string",
"projectId": "string",
"type": "public",
"title": "string",
"slug": "string",
"description": "string",
"body": "string",
"url": "string",
"state": "draft",
"order": -9007199254740991,
"collectionId": "string",
"authorId": "string",
"views": -9007199254740991,
"conversions": -9007199254740991,
"happyReactions": -9007199254740991,
"neutralReactions": -9007199254740991,
"sadReactions": -9007199254740991,
"author": {
"id": "string",
"image": "string",
"name": "string"
},
"collection": {
"helpCenterId": "string",
"name": "string"
}
}{
"code": "BAD_REQUEST",
"message": "Invalid input data",
"issues": []
}{
"code": "UNAUTHORIZED",
"message": "Authorization not provided",
"issues": []
}{
"code": "FORBIDDEN",
"message": "Insufficient access",
"issues": []
}{
"code": "NOT_FOUND",
"message": "Not found",
"issues": []
}{
"code": "INTERNAL_SERVER_ERROR",
"message": "Internal server error",
"issues": []
}List Articles
Lists a project's articles for management views, covering drafts and internal articles that never appear in public search. Paginated, returning `data` alongside a `total` for the filter you applied.
Create Article
Creates a knowledge-base article. The URL slug is generated from the title rather than supplied. Public articles belong to a collection and appear on the help center once published; internal articles are not browsable and exist to answer support questions. Requires a logged-in user. The caller becomes the article's author, so an API key alone is not enough.