Hashnode posting settings

Every post to Hashnode carries a settings object with "__type": "hashnode", a title, a publication and at least one tag. Read the live schema for your channel with Get a channel’s settings. A Hashnode channel connects with a personal access token, which only the app’s connect form takes. Connect it in the app first, then post to it here. Hashnode answers only for publications on its Pro plan, so a post to one without Pro fails when it is published.

Fields

Field	Type	Required	What it does
`__type`	string	No	Always `"hashnode"`. PostQueen sets it from the channel you post to, so it can be left out.
`title`	string	Yes	The article title, at least 6 characters.
`subtitle`	string	No	A subtitle, at least 2 characters when you send one.
`main_image`	object	No	The cover image, `{ "id": "...", "path": "..." }` as upload a file returns it. Hashnode is sent its address.
`canonical`	string	No	Where the article first appeared, as a web address.
`publication`	string	Yes	The id of the publication to publish in, from the `publications` tool.
`tags`	array	Yes	At least 1 tag, each `{ "value": "javascript", "label": "JavaScript" }`. `value` is the tag’s `slug` or `objectID` from the `tagsList` tool, and `label` its name.

The body comes from value[0].content as Markdown. The article is always published, never saved as a Hashnode draft. Hashnode has no follow-ups, so entries after the first in value are not published, and media in value is not sent: only main_image reaches Hashnode. The composer lets a person pick up to 4 tags. Hashnode itself takes up to 15.

Find publications and tags

Two tools answer them. Call them through trigger a provider tool, with no data:

curl -X POST "https://api.postqueen.ai/public/v1/integration-trigger/YOUR_CHANNEL_ID" \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"methodName": "publications", "data": {}}'

Tool	Answers	Use it for
`publications`	`[{ "id": "...", "name": "My blog" }, ...]`, your first 50	`publication`: send the `id`
`tagsList`	`[{ "name": "JavaScript", "slug": "javascript", "objectID": "...", "logo": "..." }, ...]`	`tags`: send `slug` or `objectID` as `value` and `name` as `label`

Each answer comes wrapped in { "output": ... }. A value that is not in the list is sent to Hashnode as a slug, with label as the name.

What PostQueen checks

A post that breaks one of these rules is refused with 400 before it is scheduled:

Rule	Message
A title of at least 6 characters	“title must be longer than or equal to 6 characters”
A subtitle, when sent, of at least 2 characters	“subtitle must be longer than or equal to 2 characters”
A publication	“publication should not be null or undefined”
At least 1 tag	“tags must contain at least 1 elements”
`canonical` is a web address	“Invalid URL”
The body within 10,000 characters	“post is too long, please fix it”

The settings rules come back as a list, with each field’s path:

{
  "statusCode": 400,
  "message": ["posts.0.settings.tags must contain at least 1 elements"],
  "error": "Bad Request"
}

The text limit comes back with the channel’s name instead, as on posting settings by network. The Pro plan is not checked first. When Hashnode refuses the article, the post fails with Hashnode’s own message, and a token Hashnode no longer accepts marks the channel for reconnection.

Examples

Send each body to create a post. Replace YOUR_CHANNEL_ID with the channel’s id from list channels, YOUR_PUBLICATION_ID with an id from the publications tool, and the media id and path with the values upload a file returns.

{
  "type": "schedule",
  "date": "2026-10-01T09:00:00.000Z",
  "shortLink": false,
  "tags": [],
  "posts": [
    {
      "integration": { "id": "YOUR_CHANNEL_ID" },
      "value": [
        {
          "content": "## The short version\n\nAn index on the right column took our slowest query from 4 seconds to 40 milliseconds.",
          "image": []
        }
      ],
      "settings": {
        "__type": "hashnode",
        "title": "How one index made our dashboard fast",
        "subtitle": "A Postgres story in three queries",
        "main_image": { "id": "MEDIA_ID", "path": "https://uploads.postqueen.ai/index-cover.png" },
        "publication": "YOUR_PUBLICATION_ID",
        "tags": [
          { "value": "javascript", "label": "JavaScript" },
          { "value": "web-development", "label": "Web Development" }
        ]
      }
    }
  ]
}

{
  "type": "schedule",
  "date": "2026-10-01T09:00:00.000Z",
  "shortLink": false,
  "tags": [],
  "posts": [
    {
      "integration": { "id": "YOUR_CHANNEL_ID" },
      "value": [
        { "content": "This article first appeared on our company blog.", "image": [] }
      ],
      "settings": {
        "__type": "hashnode",
        "title": "Our year in open data",
        "canonical": "https://example.com/blog/year-in-open-data",
        "publication": "YOUR_PUBLICATION_ID",
        "tags": [{ "value": "python", "label": "Python" }]
      }
    }
  ]
}

Get started

Endpoints

Posting settings by network

Build on PostQueen

SDK and no-code

Fields

Find publications and tags

What PostQueen checks

Examples

​Fields

​Find publications and tags

​What PostQueen checks

​Examples

​Related

Fields

Find publications and tags

What PostQueen checks

Examples

Related