API Markdown2HTML

Transformez vos packages ZIP Markdown en HTML prêt pour la production

Téléversez une archive ZIP contenant du Markdown et des images locales. Le système traite les ressources, corrige les références et produit un HTML prêt pour la prévisualisation, la distribution et les flux de travail en aval.

Importez l’article et ses images ensemble

  • Importation ZIP sans avoir à téléverser manuellement chaque image
  • Les images sont traitées et téléversées, tandis que le ZIP lui-même n'est jamais envoyé vers le stockage objet (COS)
  • Chemins de répertoires, styles de thèmes, articles enregistrés et documentation lisible par IA dans un seul flux
Base URL: https://api.imgto.link

Ingestion orientée ZIP

Conçu pour les exportations de packages Obsidian et Markdown avec des références d'images relatives.

Sortie HTML, prête à l'emploi

Recevez un HTML que vous pouvez prévisualiser, publier ou transmettre en aval sans nettoyage manuel supplémentaire.

Rendu adapté aux thèmes

Maintenez une cohérence stylistique sur l'ensemble de vos contenus de marque, bases de connaissances et flux de travail par lots.

Ressources organisées automatiquement

Les articles et les ressources restent parfaitement organisés pour faciliter la recherche, la réutilisation et la collaboration en équipe.

Cas d'utilisation typiques

  1. 1

    Regroupez vos articles Markdown provenant d'Obsidian, d'une base de connaissances ou de fichiers éditoriaux locaux dans une archive ZIP.

  2. 2

    Laissez le système gérer automatiquement le téléversement des images, le remplacement des références et la conversion de la mise en page.

  3. 3

    Intégrez le résultat généré dans vos pipelines de publication, de distribution, d'enrichissement par IA ou d'édition interne.

Ce que vous obtenez en pratique

  • Contenu HTML prêt pour la prévisualisation, l'intégration ou la publication en aval
  • Matériel d'article avec des références d'images déjà nettoyées pour une édition ultérieure
  • Une structure de ressources plus stable pour la collaboration, l'archivage et la gestion par lots
  • Un rendu visuel cohérent pour les packages Markdown provenant de différentes sources

Clés API et documentation lisible par IA

La section ci-dessous sert à la fois de console développeur et de document de transfert prêt à copier pour l'intégration IA.

Documentation de l'API d'importation ZIP

Créez une clé API en un clic, puis copiez le guide Markdown ci-dessous pour votre agent IA ou votre équipe d'ingénierie.

Créer une clé API d'importation

Veuillez vous connecter pour accéder à cette fonctionnalité

Clés existantes

Aucune clé API pour le moment

Identifiants API des thèmes

Chaque themeId correspond au nom du thème affiché dans l'éditeur. Les noms lisibles par l'homme et les couleurs de référence sont listés ci-dessous.

Thème par défaut
themeId: warm
Système
Classique, chaleureux
#ea580c
#333
Style Chinois
themeId: china
Noto Serif
Classique, élégant
#7f1d1d
#292524
#f5f5f4
Cyberpunk
themeId: cyber
Monospace
Futur, néon, tech
#ec4899
#a855f7
#3b82f6
WeChat Classique
themeId: classic
Sans
Propre, sûr, polyvalent
#07c160
#333
Ink Serif
themeId: ink
Song (Serif)
Culture, histoire, tradition
#3f3f46
#78716c
Magazine Éditorial
themeId: editorial
Serif + Sans
Mode, art, gris premium
#1f2937
#ef4444
Guérison WenKai
themeId: wenkai
WenKai
Émotionnel, quotidien, manuel
#57534e
#78716c
Lecture Profonde
themeId: business
Sans système
Affaires, technologie, tutoriels
#1e3a8a
#1e40af
Sentier Forestier
themeId: forest
Sans
Nature, voyages, frais
#059669
#ecfdf5
Côte d'Azur
themeId: azure
Sans
Tech, été, léger
#0ea5e9
#e0f2fe
Café Douillet
themeId: coffee
Serif
Vintage, histoires, chaleur
#78350f
#fffbeb
Cyber Néon
themeId: neon
Mono
Geek, futuriste, tendance
#d946ef
#06b6d4
Rouge Oriental
themeId: red
Serif
National, festif, élégant
#be123c
#fff1f2
Argent Tech
themeId: silver
Sans
Rationnel, froid, professionnel
#475569
#e2e8f0
Blanc Minimal
themeId: minimal
Sans
Photographie, design, calme
#000
#999
Rose Morandi
themeId: morandi
Serif
Beauté, féminine, douce
#be185d
#fbcfe8
Vibes Ensoleillées
themeId: sunny
Ludique
Nourriture, shopping, jeunesse
#f97316
#fbbf24
Été Menthe
themeId: mint
Sans Arrondi
Rafraîchissant, vie, guérison
#10b981
#d1fae5
Automne Doré
themeId: autumn
Serif
Chaleur, histoires, sentiments
#d97706
#fef3c7
Provence
themeId: lavender
Serif
Onirique, romantique, esthétique
#8b5cf6
#ede9fe
Film Vintage
themeId: vintage
Sans
Rétro, atmosphérique, critiques
#7f1d1d
#fecaca
Notes d'Étude
themeId: notes
WenKai
Surlignage, manuel, astuces
#facc15
#fef08a
Gris Fumé
themeId: grey
Sans
Minimaliste, frais, texturé
#374151
#f3f4f6

Guide d'intégration API lisible par IA

Imgto.link Markdown ZIP Import API

What this API does

  • Upload one ZIP package containing one Markdown file and its local images
  • Queue an asynchronous import job
  • Automatically create the target image directory if it does not exist
  • Automatically save the imported Markdown into the article folder 公众号
  • Upload referenced images to Imgto.link storage
  • Replace local image references in Markdown
  • Return the final resolved Markdown, HTML output, saved article info, and image directory path after the job completes

Base URL

https://api.imgto.link

Endpoints on the same host

  • ZIP upload endpoint: POST https://api.imgto.link/uploads/md-import
  • Create import job: POST https://api.imgto.link/api/v1/md/import
  • Poll job status: GET https://api.imgto.link/api/v1/md/import/jobs/{jobId}
  • In production you can proxy the control-plane routes on the same https://api.imgto.link host, so clients only need one public base URL.

Authentication

Use an API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Async workflow

  1. Upload the ZIP archive to the upload endpoint and get back uploadRelativePath
  2. Create an async import job with POST https://api.imgto.link/api/v1/md/import
  3. Poll GET https://api.imgto.link/api/v1/md/import/jobs/{jobId} until the job reaches a terminal status

Step 1: upload ZIP archive

Endpoint

POST https://api.imgto.link/uploads/md-import

Content-Type

multipart/form-data

Form fields

  • archive (required): ZIP file containing one Markdown file and its local image files

Success response

{
  "code": 200,
  "data": {
    "relativePath": "inbox/2026/03/12/uuid-article-package.zip",
    "originalFilename": "article-package.zip",
    "size": 345678,
    "uploadedAt": "2026-03-12T08:00:00.000Z"
  }
}

Step 2: create import job

Endpoint

POST https://api.imgto.link/api/v1/md/import

Content-Type

application/json

Request body

{
  "uploadRelativePath": "inbox/2026/03/12/uuid-article-package.zip",
  "archiveFilename": "article-package.zip",
  "archiveSize": 345678,
  "themeId": "classic",
  "directoryPath": "public/articles/demo",
  "entryMarkdown": "docs/index.md",
  "saveFolderId": 12,
  "mdfileId": 123
}

Request field notes

  • uploadRelativePath (required): value returned from step 1
  • archiveFilename (required): original zip filename
  • archiveSize (optional): archive size in bytes
  • themeId (optional): theme API name, default is classic
  • directoryPath (optional): base upload directory path like public/articles/launch-2026
  • entryMarkdown (optional): specific markdown file path inside the ZIP when there are multiple markdown files
  • saveFolderId (optional): target markdown folder ID in the editor
  • mdfileId (optional): existing markdown article ID. When provided, the import is treated as a replace/update. The old article and its imported images are deleted before the new content is saved

Success response

{
  "code": 202,
  "message": "Accepted",
  "data": {
    "jobId": "mdi_1234567890abcdef",
    "status": "QUEUED",
    "progress": 0,
    "pollUrl": "/api/v1/md/import/jobs/mdi_1234567890abcdef"
  }
}

Step 3: poll job status

Endpoint

GET https://api.imgto.link/api/v1/md/import/jobs/{jobId}

Non-terminal response example

{
  "code": 200,
  "message": "Ok",
  "data": {
    "jobId": "mdi_1234567890abcdef",
    "status": "PROCESSING",
    "progress": 65,
    "currentStage": "processing_images",
    "message": "正在处理图片 2/4",
    "compensationStatus": "NOT_REQUIRED",
    "updatedAt": "2026-03-12T08:01:15.000Z"
  }
}

Completed response example

{
  "code": 200,
  "message": "Ok",
  "data": {
    "jobId": "mdi_1234567890abcdef",
    "status": "SUCCEEDED",
    "progress": 100,
    "currentStage": "completed",
    "message": "导入完成",
    "compensationStatus": "NOT_REQUIRED",
    "updatedAt": "2026-03-12T08:01:30.000Z",
    "result": {
      "mdfileId": 123,
      "resolvedMarkdown": "# Title\n\n![cover](https://...)",
      "html": "<section>...</section>",
      "wechatApiHtml": "<section>...</section>",
      "imageDirectoryPath": "public/公众号/my-article",
      "savedArticle": {
        "id": 123,
        "mdfileId": 123,
        "title": "My Article",
        "folder": {
          "id": 9,
          "name": "公众号",
          "fullPath": "公众号"
        }
      }
    }
  }
}

Failed response example

{
  "code": 200,
  "message": "Ok",
  "data": {
    "jobId": "mdi_1234567890abcdef",
    "status": "FAILED_COMPENSATED",
    "progress": 100,
    "currentStage": "failed",
    "message": "导入失败,已回滚上传图片与用户额度",
    "compensationStatus": "COMPLETED",
    "updatedAt": "2026-03-12T08:02:00.000Z",
    "error": {
      "message": "Referenced image not found: ./images/cover.png"
    }
  }
}

Job status notes

  • Terminal success status: SUCCEEDED
  • Terminal failure status: FAILED_COMPENSATED
  • Transitional failure statuses can appear briefly during rollback, such as FAILED_PENDING_COMPENSATION and FAILED_COMPENSATION_ERROR
  • result is returned only when the job succeeds
  • error is returned when the job fails

Result field notes

  • result.resolvedMarkdown: Markdown after local image paths are replaced with Imgto.link URLs
  • result.html: Base rendered HTML for preview or debugging
  • result.wechatApiHtml: Recommended HTML for submitting to the WeChat Official Account API content field
  • result.mdfileId: The saved Markdown article ID, returned for convenient reuse in the next replace import request
  • result.savedArticle: Saved Markdown article record in the editor
  • result.savedArticle.mdfileId: Stable article identifier to pass back on the next import if you want to replace this article instead of creating a new one
  • result.imageDirectoryPath: Final image upload directory path

Example cURL: step 1 upload

curl -X POST "https://api.imgto.link/uploads/md-import" \
  -F "archive=@article-package.zip" \

Example cURL: step 2 create job

curl -X POST "https://api.imgto.link/api/v1/md/import" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "uploadRelativePath": "inbox/2026/03/12/uuid-article-package.zip",
    "archiveFilename": "article-package.zip",
    "archiveSize": 345678,
    "themeId": "classic",
    "directoryPath": "public/articles/demo"
  }'

Example cURL: step 3 poll job

curl -X GET "https://api.imgto.link/api/v1/md/import/jobs/mdi_1234567890abcdef" \
  -H "Authorization: Bearer YOUR_API_KEY"

Example JavaScript: end-to-end async import

const uploadFormData = new FormData();
uploadFormData.append("archive", zipFile);

const uploadResponse = await fetch("https://api.imgto.link/uploads/md-import", {
  method: "POST",
  body: uploadFormData
});

const uploadResult = await uploadResponse.json();
const relativePath = uploadResult.data.relativePath;

const createResponse = await fetch("https://api.imgto.link/api/v1/md/import", {
  method: "POST",
  headers: {
    Authorization: "Bearer YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    uploadRelativePath: relativePath,
    archiveFilename: uploadResult.data.originalFilename,
    archiveSize: uploadResult.data.size,
    themeId: "classic",
    directoryPath: "public/articles/demo"
  })
});

const createResult = await createResponse.json();
const jobId = createResult.data.jobId;

let finalResult = null;

for (;;) {
  const pollResponse = await fetch("https://api.imgto.link/api/v1/md/import/jobs/" + jobId, {
    method: "GET",
    headers: {
      Authorization: "Bearer YOUR_API_KEY"
    }
  });

  const pollResult = await pollResponse.json();
  const job = pollResult.data;

  if (job.status === "SUCCEEDED") {
    finalResult = job.result;
    break;
  }

  if (job.status === "FAILED_COMPENSATED") {
    throw new Error(job.error?.message || "Import failed");
  }

  await new Promise((resolve) => setTimeout(resolve, 1800));
}

console.log(finalResult.mdfileId);
console.log(finalResult.resolvedMarkdown);
console.log(finalResult.wechatApiHtml);
console.log(finalResult.savedArticle);

Example: replace an existing imported article

Use the result.savedArticle.mdfileId returned by the previous successful import job.

const replaceResponse = await fetch("https://api.imgto.link/api/v1/md/import", {
  method: "POST",
  headers: {
    Authorization: "Bearer YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    uploadRelativePath: uploadedZip.data.relativePath,
    archiveFilename: uploadedZip.data.originalFilename,
    archiveSize: uploadedZip.data.size,
    themeId: "classic",
    mdfileId: previousResult.savedArticle.mdfileId
  })
});

const replaceResult = await replaceResponse.json();
console.log(replaceResult.data.jobId);

Replace behavior

  • mdfileId omitted: create a new import job using the uploaded ZIP
  • mdfileId provided: force this import to replace that exact article
  • During replacement, the job deletes the old markdown record first
  • It also deletes images previously imported for that markdown article before uploading the new images
  • Read the latest mdfileId from the final successful poll result and keep using it for future updates

Example: publish to WeChat Official Account draft API

Use result.wechatApiHtml from the completed import job for the content field instead of result.html.

const completedImport = await waitForImportJob(jobId);
const wechatApiHtml = completedImport.result.wechatApiHtml;

const draftPayload = {
  articles: [
    {
      title: completedImport.result.savedArticle?.title || "Imported article",
      author: "Your Team",
      digest: "",
      content: wechatApiHtml,
      content_source_url: "",
      thumb_media_id: "YOUR_WECHAT_THUMB_MEDIA_ID",
      need_open_comment: 0,
      only_fans_can_comment: 0
    }
  ]
};

const wechatResponse = await fetch(
  "https://api.weixin.qq.com/cgi-bin/draft/add?access_token=YOUR_WECHAT_ACCESS_TOKEN",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json"
    },
    body: JSON.stringify(draftPayload)
  }
);

const wechatResult = await wechatResponse.json();
console.log(wechatResult);

WeChat publishing note

  • Prefer result.wechatApiHtml for WeChat Official Account API publishing
  • Do not use result.html as the content field if you need output aligned with the website's copy/export flow
  • Image URLs inside result.wechatApiHtml should already point to uploaded Imgto.link assets
  • You still need to provide your own WeChat access_token and thumb_media_id

Theme API names

  • Thème par défaut (warm): #ea580c, #333
  • Style Chinois (china): #7f1d1d, #292524, #f5f5f4
  • Cyberpunk (cyber): #ec4899, #a855f7, #3b82f6
  • WeChat Classique (classic): #07c160, #333
  • Ink Serif (ink): #3f3f46, #78716c
  • Magazine Éditorial (editorial): #1f2937, #ef4444
  • Guérison WenKai (wenkai): #57534e, #78716c
  • Lecture Profonde (business): #1e3a8a, #1e40af
  • Sentier Forestier (forest): #059669, #ecfdf5
  • Côte d'Azur (azure): #0ea5e9, #e0f2fe
  • Café Douillet (coffee): #78350f, #fffbeb
  • Cyber Néon (neon): #d946ef, #06b6d4
  • Rouge Oriental (red): #be123c, #fff1f2
  • Argent Tech (silver): #475569, #e2e8f0
  • Blanc Minimal (minimal): #000, #999
  • Rose Morandi (morandi): #be185d, #fbcfe8
  • Vibes Ensoleillées (sunny): #f97316, #fbbf24
  • Été Menthe (mint): #10b981, #d1fae5
  • Automne Doré (autumn): #d97706, #fef3c7
  • Provence (lavender): #8b5cf6, #ede9fe
  • Film Vintage (vintage): #7f1d1d, #fecaca
  • Notes d'Étude (notes): #facc15, #fef08a
  • Gris Fumé (grey): #374151, #f3f4f6

ZIP package rules

  • Include exactly one Markdown file, or pass entryMarkdown
  • Reference local images with relative paths such as ./images/a.png
  • Remote image URLs are kept as-is
  • The API converts static images to AVIF by default
  • The imported Markdown is automatically saved to the article folder 公众号
  • The image upload directory becomes {directoryPath}/{article-slug}

AI integration instruction

If you give this API to an AI coding assistant, tell it:

"Use the async workflow. First upload the ZIP to https://api.imgto.link/uploads/md-import with multipart/form-data and read data.relativePath, data.originalFilename, and data.size. Then call POST https://api.imgto.link/api/v1/md/import with JSON using uploadRelativePath, archiveFilename, and optional themeId, directoryPath, entryMarkdown, saveFolderId, and mdfileId. Authenticate the control-plane API with Authorization: Bearer YOUR_API_KEY. Then poll GET https://api.imgto.link/api/v1/md/import/jobs/{jobId} until status becomes SUCCEEDED or FAILED_COMPENSATED. On success, read result.resolvedMarkdown, result.wechatApiHtml, result.savedArticle, result.mdfileId, and result.imageDirectoryPath. Prefer result.wechatApiHtml when publishing to the WeChat Official Account API content field."

Voir le Markdown brut