What Is the Newspic Draft API?

"What is the newspic draft API?"

The shortest answer is this:

It is a draft endpoint for image-first content, where text and multiple images are submitted together as a draft.

That makes it different from a standard article draft. The two endpoints target different content structures.

Why it should not be treated as the same as a normal article draft

It is easy to assume that both are just "draft APIs" for the WeChat ecosystem. In practice, the content model is different.

A standard article draft usually looks like:

• a title
• a cover image
• Markdown or HTML body content

A newspic draft is closer to:

• a title
• lighter body text
• multiple images grouped as content blocks

That difference is enough to justify a separate endpoint and a separate integration path.

What the public example looks like

The current example endpoint is:

POST /api/v1/newspic-draft

Authentication headers include:

• Wechat-Appid
• Wechat-App-Secret
• Md2wechat-API-Key

A minimum request body looks like this:

{
  "title": "Newspic title",
  "content": "Body text",
  "imageUrls": [
    "https://example.com/1.jpg",
    "https://example.com/2.jpg"
  ]
}

That request shape already shows the main distinction: this is a lighter, image-first draft flow.

Where it fits best

The newspic draft API is a good fit for:

• image-driven content
• workflows that need to turn multiple images into a draft quickly
• agent pipelines that generate short text first and attach images after
• teams that automate lighter content formats, not just long-form articles

It is not the best default for every article. It is best when images are central to the structure.

The main difference from a standard article draft

A simple way to separate them:

Standard article draft

Better for long-form Markdown, theme-based formatting, and a fuller article structure.

Newspic draft

Better for a title, lighter text, and an image array.

This is not just a naming difference. It changes:

• the input shape
• the content type the endpoint expects
• the downstream publishing model

Why separate endpoints make the workflow easier

When the product surface is split into:

• conversion
• article draft
• newspic draft
• media upload

the caller can choose the right path with less guesswork.

That is usually better than hiding multiple content models behind one large request format.

What to validate before you integrate it

At minimum, confirm these points first:

• you already have an Md2wechat-API-Key
• you have Wechat-Appid
• you have Wechat-App-Secret
• image URLs are reachable and stable

If those conditions are missing, a structurally correct request can still fail in practice.

How it relates to the Convert API

The newspic draft API is not a replacement for Markdown conversion.

A simpler distinction is:

• Convert API solves Markdown to WeChat HTML
• Newspic draft solves direct draft creation for an image-first content shape

These are different layers of the workflow.

Closing thought

The newspic draft API matters because image-first content should not be forced through a long-form article shape.

If your workflow needs to push lighter, multi-image content into the WeChat draft flow, this endpoint is the clearer path.