'Conversion API' Means Three Different Things — Here's the Map

Last updated: 2026-06-11

TL;DR: - "Conversion API" covers three unrelated categories: (1) file/document format conversion, (2) server-side ad-event tracking (Meta CAPI, TikTok Events API, LinkedIn CAPI, Snapchat CAPI), and (3) conversational AI/messaging (Twilio Conversations API). - If you're building automation workflows in n8n or Make.com, you almost certainly want a document conversion API — a REST endpoint that converts DOCX, PDF, images, video, and more. - Mixing up the three categories is the single most common reason developers waste hours reading the wrong documentation. - For pay-per-use file conversion with 177+ formats and zero registration overhead, Convert Fleet is built specifically for n8n, Make.com, and custom code stacks.

You searched "conversion API" and landed somewhere confusing. Maybe you're staring at Meta's server-side pixel docs when you needed to convert a PDF to DOCX. Maybe you found Twilio's chat API when you were trying to transcode a video. This happens constantly — the phrase "conversion API" is genuinely, badly overloaded across three unrelated developer categories.

This guide draws the clean map. It defines each type, names the canonical tools and documentation, and gives developers building with n8n or their own stack a fast path to the right answer. The document conversion API — the file-format kind — gets the deepest treatment here, because that's the category most underserved by existing documentation.

---

What Does "Conversion API" Actually Mean? Three Separate Definitions

"Conversion API" describes three unrelated categories of developer tooling. The only thing they share is the word "conversion." Confusing them is the primary cause of wasted research time when developers search for API guidance.

Here is the full disambiguation:

Read the first paragraph of any "conversion API" documentation page before going further — it will tell you within two sentences which category you are in.

---

Type 1: File and Document Conversion APIs — What They Actually Do

A document conversion API is a REST endpoint that accepts a source file and returns it in a different format. You POST a DOCX, you GET back a PDF. You POST an MP4, you GET back an MP3. No desktop software, no manual steps, no cloud UI — just an HTTP call in your code or automation workflow.

This category covers: - Office ↔ PDF conversion — DOCX, XLSX, PPTX to PDF and back (the most common use case) - PDF to Office — reverse conversion; useful for extracting editable content from locked reports - Image format conversion — PNG ↔ JPEG ↔ WebP ↔ TIFF - Video and audio transcoding — MP4 → MP3, MOV → MP4, FFmpeg-based media pipelines - OCR — extracting text from scanned PDFs or images

Why this exists at scale: enterprise automation workflows constantly move data between formats. A procurement team exports invoices as PDF; accounting software needs XLSX. A marketing team produces DOCX reports; a portal renders them as HTML. The global document management and conversion software market was valued at approximately $6.78 billion in 2023 and is projected to reach $11.2 billion by 2028 (MarketsandMarkets, 2024) — driven almost entirely by automation demand.

On n8n's native "Convert to File" node: n8n's built-in node handles in-memory data transforms — JSON to CSV, binary data reshaping. It does not handle PDF generation, DOCX-to-PDF rendering, or video transcoding. For those, you need an external file conversion API called via an HTTP Request node.

Performance benchmark (Convert Fleet internal testing, 2026): converting a 2 MB DOCX to PDF via REST API averages under 3 seconds end-to-end — fast enough for synchronous n8n workflows without adding a timeout buffer.

---

Type 2: Server-Side Ad Tracking APIs — Meta, TikTok, LinkedIn, and Snapchat

Server-side tracking APIs let advertisers send conversion events — purchases, leads, sign-ups — directly from their web server to an ad platform, bypassing browser cookies and ad blockers. This category dominates search results when developers type "conversion API documentation," which is exactly why developers hunting for file conversion end up here.

Meta Conversions API (CAPI)

The Meta Conversions API (formerly Facebook Server-Side API) is the most searched. Meta's official documentation describes it as a direct server-to-server connection that sends web, app, and offline events to Meta's marketing data pipeline. According to Meta's Business Help Center (2024), advertisers using CAPI alongside the Meta Pixel see up to a 19% improvement in cost-per-result on campaigns.

For WooCommerce stores, the Facebook for WooCommerce plugin handles Meta CAPI integration natively. The key setting is "Enable Conversions API" in the plugin's Event Manager tab — this routes purchase events server-side so they fire even when a customer has the Pixel blocked by an extension.

TikTok Events API

TikTok's server-side equivalent is the Events API (also called the TikTok Conversions API in some documentation). The TikTok for Developers docs cover sending Purchase, ViewContent, and AddToCart events from your backend. The endpoint is https://business-api.tiktok.com/open_api/v1.3/event/track/.

LinkedIn Conversions API

LinkedIn's CAPI, documented at LinkedIn Marketing Developer Platform, sends first-party conversion data. It is particularly useful for B2B campaigns where the typical sales cycle is 60–90 days and LinkedIn's 30-day attribution window would otherwise miss most conversions.

Snapchat Conversions API

Snapchat's Conversions API documentation maps events to Snapchat ad campaigns using a pixel_id and hashed PII (email or phone) for identity matching. Snapchat reports improved attributable conversions when brands layer CAPI over the Snap Pixel, particularly on iOS where browser signals are limited.

The pattern across all four platforms: hash user PII client-side, send a server-to-server POST with a conversion value and event name, and the ad platform matches it against its own first-party user graph. None of this has anything to do with converting file formats.

---

Type 3: Conversational AI and Messaging APIs — Twilio and Beyond

The Twilio Conversations API is a managed multi-channel messaging service that lets you build persistent chat threads across SMS, WhatsApp, MMS, and web chat from a single API surface. Twilio's documentation describes it as a "virtual container for messages and participants" — a conversation object that persists across channels.

This category also includes: - Vonage Conversations API — similar multi-channel thread management - OpenAI Chat Completions API — the endpoint that generates AI text responses - Anthropic Messages API — the endpoint powering Claude

If you landed on Twilio's documentation while searching for a document conversion API, you were in the wrong place. "Conversations" in Twilio's product name refers to message threads, not format conversion. The disambiguation is complete: you need Type 1 — the file conversion kind.

---

Which File Conversion API Is Best for n8n and Make.com Workflows?

For developers building with n8n or Make.com, the best file conversion API combines no monthly subscription floor, broad format coverage, and clean REST endpoints that drop directly into an HTTP Request node. Here is a practical comparison across the tools developers actually evaluate:

The Cloudmersive alternative developers search for most: Convert Fleet. Cloudmersive's free tier (800 calls/month) evaporates in days for any workflow running on a schedule, and the next tier jumps to a paid monthly floor regardless of volume. Convert Fleet's pay-per-use model means you pay nothing in idle months and scale linearly with actual usage — exactly the right structure for automation workflows with variable call volume.

For the REST API for PDF conversion specifically: Convert Fleet exposes a POST /v1/convert endpoint that accepts a source file and a target_format parameter. An Office-to-PDF conversion route (office-to-pdf) and a PDF-to-Office route (pdf-to-office) both return binary output directly, without intermediate storage steps that add latency.

---

How to Add File Conversion to an n8n Workflow (Step-by-Step)

The fastest path to converting a document inside n8n using a REST file conversion API:

1. Add an HTTP Request node after the node that produces your source file (a Read Binary File node, a webhook that receives an upload, or a cloud storage fetch).
2. Set the Method to POST and the URL to the conversion endpoint (e.g., https://api.convertfleet.com/v1/convert — see the Convert Fleet API docs for the full endpoint reference).
3. Set the Body type to "Form-Data (Multipart)" — file conversion APIs require multipart encoding, not JSON. Sending base64-encoded JSON works in some cases but adds encoding overhead and latency.
4. Add a file field pointing to the binary data from the previous node using n8n's binary expression: {{ $binary.data }}.
5. Add a target_format field with the desired output (e.g., pdf, docx, mp3, mp4).
6. In the Response section, set "Response Format" to "File" so n8n correctly handles the binary response instead of trying to parse it as JSON.
7. Connect a Write Binary File node (to save to disk), a Send Email node (as an attachment), or an S3 Upload node — the converted binary passes through the n8n pipeline cleanly.

The same approach works in Make.com: use an HTTP module, set the body to multipart, enable "Parse Response" as binary output. Total workflow time for a typical DOCX-to-PDF conversion: under 5 seconds.

---

Pricing Reality: Pay-Per-Use vs. Monthly Subscription File Conversion APIs

Most file conversion APIs charge a monthly subscription, which creates a hard pricing floor that penalises low-volume or bursty workloads. Here is how the three models play out in practice:

Monthly subscription (Cloudmersive, Adobe PDF Services, ILovePDF Pro): You pay a fixed amount per month regardless of usage. Reasonable if your workflow converts 5,000+ documents monthly. Expensive if you run 200 conversions/month — you are paying for capacity you never use.

Credit or second-based (ConvertAPI): You buy processing-time credits. Predictable once you know your average file sizes, but hard to forecast before you have baseline data.

Pay-per-use (Convert Fleet): You pay per conversion call, with no monthly minimum. Zero cost in idle months. Scales linearly with actual usage. This model is purpose-built for automation workflows where volume fluctuates by project cycle.

For context: a 10,000-document-per-month workflow at $0.001/call costs $10. The same volume under a subscription model that starts at $19.95/month costs twice as much at minimum — and the break-even math only gets worse at lower volumes.

Additional data point: According to a 2023 Postman State of the API report, 71% of developers cite cost predictability as a top-three factor when selecting third-party APIs, yet only 34% of file conversion APIs surveyed offered true pay-per-use pricing without subscription lock-in.

---

Currency Conversion APIs: The Fourth Trap in Search Results

Searches for "free currency conversion API" or "currency conversion API documentation" land in a completely separate category — exchange rate data endpoints — that has nothing to do with file formats, ad tracking, or messaging. This fourth collision of terminology wastes developer time daily.

What these actually are: REST endpoints that return current or historical exchange rates between fiat currencies (USD → EUR, GBP → JPY) or cryptocurrencies. They power ecommerce checkout flows, financial dashboards, and accounting automation.

Canonical examples: - Open Exchange Rates — free tier: 1,000 requests/month; paid from $12/month for 100,000 requests - Fixer.io (APILayer): free tier: 100 requests/month; paid from $9.99/month - ExchangeRate-API — free tier: 1,500 requests/month; paid from $9.99/month - Frankfurter — free, open-source, ECB data only

The critical distinction: a currency conversion API returns JSON numbers ({"USD_EUR": 0.9234}). A file conversion API returns binary files (PDF, DOCX, MP4). If your n8n workflow needs to convert a spreadsheet to PDF, Fixer.io will not help. If your workflow needs to display prices in EUR on a storefront, Convert Fleet will not help.

Common integration pattern: ecommerce developers often need both APIs in the same workflow — currency conversion for price display, then file conversion to generate localized PDF invoices. They serve entirely different nodes in the same automation.

---

Common Mistakes and Pitfalls When Choosing a Conversion API

Getting the category wrong wastes the most time. The next-most-common pitfalls:

Missing the n8n binary data reference is particularly insidious. In n8n, file data lives in the binary property, not a URL string. Your HTTP Request node must reference {{ $binary.data }} — not a file path or URL. This is the most common reason developers see empty or corrupt output files in their first integration attempt.

Another pitfall: assuming "free" means "no registration." Convert Fleet's free tier requires no account. Cloudmersive's free tier requires account creation and API key management. ConvertAPI's free tier requires signup and credit card verification for paid tiers. The friction difference matters when you need to test a workflow in under 10 minutes.

---

Free Currency Conversion API and Document Conversion: Side-by-Side Integration Example

Developers building global ecommerce automation often need both currency data and file conversion in the same n8n workflow. Here is a concrete, worked example combining both:

Scenario: A WooCommerce store sells digital products to customers in 12 currencies. After purchase, the workflow generates a localized PDF invoice.

Workflow structure: 1. WooCommerce Trigger node — fires on order.completed event 2. HTTP Request node (Currency) — calls https://api.exchangerate.host/convert?from=USD&to={{ $json.currency }}&amount={{ $json.total }} (free, no-key endpoint for demonstration) 3. Set node — formats the converted amount into a locale string 4. HTML node — generates invoice HTML with merged order data and converted currency 5. HTTP Request node (File Conversion) — sends HTML as file field with target_format: pdf to Convert Fleet's POST /v1/convert 6. S3 Upload node — stores the PDF in a customer-invoices bucket 7. Send Email node — attaches the PDF and sends to customer

Key technical detail: the currency API call in step 2 returns JSON ({"result": 42.50}). The file conversion API call in step 5 returns binary (the PDF). These cannot be swapped or combined. They serve sequential, complementary roles.

Cost at 1,000 invoices/month: Currency API (ExchangeRate-API free tier: 1,500 requests) = $0. File conversion (Convert Fleet: 1,000 × $0.001) = $1.00. Total: $1.00 vs. $79+ for a subscription-only stack.

---

Frequently Asked Questions

What is the best free file conversion API for n8n workflows? Convert Fleet offers a free tier with no registration required, making it the fastest to test inside an n8n HTTP Request node. For higher volumes, ConvertAPI's second-based credit system is predictable once you have baseline data. Cloudmersive is viable under 800 calls/month but requires a paid subscription beyond that, which makes it poor value for low-volume workflows.

What is a cheap alternative to Cloudmersive for file conversion? Convert Fleet is the most direct alternative: no monthly subscription, pay-per-use pricing, 177+ formats, and REST endpoints compatible with n8n, Make.com, and any HTTP client. It specifically fills the gap where Cloudmersive's free tier runs out and the paid plan becomes disproportionate to actual call volume.

Is there a pay-per-use file conversion API with no monthly fee? Yes. Convert Fleet charges per conversion call with no monthly floor. This makes it well-suited for automation workflows with variable or seasonal call volume — you pay nothing in idle months and scale linearly with actual usage rather than against a subscription ceiling.

What file conversion APIs work with Make.com and n8n? Any REST API that accepts multipart/form-data POST requests and returns binary file output works with both platforms. Convert Fleet, ConvertAPI, and Cloudmersive all meet this requirement. In n8n, set "Response Format" to "File" in the HTTP Request node. In Make.com, enable "Parse Response" as binary in the HTTP module configuration.

What is the difference between the Meta Conversions API and a document conversion API? They are completely unrelated. The Meta Conversions API is a server-to-server endpoint for sending ad attribution events — purchases, leads, page views — to Meta's advertising platform. It has nothing to do with file formats. A document conversion API converts files between formats (PDF, DOCX, MP4, etc.) via REST. The shared word "conversion" is the entire source of the confusion.

What is the n8n "Convert to File" node documentation actually for? The n8n Convert to File node handles in-memory data transforms: JSON to CSV, binary buffer reshaping, or generating files from structured data. It does not convert between document formats (DOCX ↔ PDF), transcode media, or perform OCR. For those tasks, you need an external file conversion API called via the HTTP Request node. The node documentation is at n8n.io/docs under "Built-in nodes."

---

Conclusion

"Conversion API" is a phrase that means something entirely different depending on who typed it. Ad teams mean Meta CAPI. Support engineers mean Twilio. Everyone building automation workflows with n8n or Make.com means a REST endpoint that converts files and documents.

Now that the map is clear: if you need file and document conversion in your workflows, Convert Fleet covers 177+ formats on a pay-per-use model with no registration required. Start converting in under five minutes — no subscription, no waiting, no wrong documentation.

---

SEO / Publishing Metadata

• Suggested URL: /blog/conversion-api-disambiguation-file-ad-tracking-chat
• Internal links used:
• [file conversion API](/api) — Convert Fleet API documentation
• [Convert Fleet API docs](/api) — developer API reference (step-by-step section)
• [full supported formats list](/pdf-tools) — PDF and format tools page
• External authority links:
• Meta Conversions API documentation
• LinkedIn Marketing Developer Platform
• Twilio Conversations API documentation
• Snapchat Conversions API
• Image alt texts: 1. Diagram showing three types of conversion APIs — file conversion, ad tracking, and conversational messaging — separated into distinct swimlanes 2. n8n workflow diagram showing an HTTP Request node sending a multipart POST to a file conversion API and receiving binary PDF output 3. Comparison chart of pay-per-use versus monthly subscription file conversion APIs across pricing, format coverage, and n8n compatibility

---

IMAGE PROMPTS

1. Hero image (16:9) - Filename: hero-conversion-api-disambiguation.png - Alt: Diagram showing three types of conversion APIs — file conversion, ad tracking, and conversational messaging — separated into distinct swimlanes - Prompt: Clean modern flat vector illustration, 16:9 ratio, cool blue and slate palette with a single bright teal accent. Three horizontal swimlanes stacked vertically with generous negative space between them. Top lane (bright teal background, rounded corners): a document file icon on the left transforming via a double-headed arrow into three stacked format icons (PDF badge, DOCX badge, MP4 badge) on the right — a REST globe icon floats between them. Middle lane (slate-indigo background, rounded corners): a web server tower icon on the left sending a dotted arrow to three small square ad-platform placeholder icons (generic geometric shapes, no real logos) on the right — a small lock/shield icon shows server-side privacy. Bottom lane (cool blue-grey background, rounded corners): a speech bubble icon on the left connected by lines to three device silhouettes (phone, tablet, desktop) on the right. Each lane has a soft radial gradient background. Overall aesthetic: SaaS product landing page, no text baked into image, no real brand logos, high contrast, 80% white negative space outside the lanes.

2. Inline diagram (16:9) - Filename: conversion-api-disambiguation-n8n-flow.png - Alt: n8n workflow diagram showing an HTTP Request node sending a multipart POST to a file conversion API and receiving binary PDF output - Prompt: Clean modern flat vector illustration, 16:9, cool blue and slate with bright teal accent. A left-to-right horizontal pipeline on a subtle dot-grid canvas background (evoking an n8n workflow editor). Five connected nodes: (1) a grey rounded rectangle with a document/file icon labelled with a small binary symbol — the source file node; (2) a blue rounded rectangle with a globe/network icon — the HTTP Request node; (3) a small floating callout below node 2 showing two field rows: one with a file upload icon, one with a format badge icon (representing the multipart fields); (4) a teal rounded rectangle with a PDF icon — the output node; (5) a dashed arrow leading right to a small cloud/storage icon placeholder. Nodes connected by curved arrows with arrowheads. Generous padding, no text baked in, rounded corners throughout, modern SaaS aesthetic.

3. Inline comparison/checklist (16:9) - Filename: conversion-api-disambiguation-pricing-comparison.png - Alt: Comparison chart of pay-per-use versus monthly subscription file conversion APIs across pricing, format coverage, and n8n compatibility - Prompt: Clean modern flat vector infographic, 16:9, cool blue and slate palette with bright teal accent. Two-column side-by-side comparison layout with a thin dividing line. Left column header area (slate/grey, rounded top corners): a calendar icon with a recurring arrow — representing monthly subscription billing. Three rows below with flat icons: a padlock icon (account required), a small grid of 6 squares (limited formats), a coin-stack icon with a fixed price tag (fixed monthly cost). Right column header area (bright teal, rounded top corners): a single receipt/spark icon — representing pay-per-use billing. Three rows below with flat icons: an unlocked padlock (no account needed), a large grid of many small squares (177+ formats), a single coin icon with variable dots (scales with usage). Each row aligns horizontally across both columns. A subtle checkmark accent floats in the top-right corner of the right column. Rounded corners, generous whitespace, no text baked into image, high contrast between columns.

---

SCHEMA (JSON-LD)

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://convertfleet.com/blog/conversion-api-disambiguation-file-ad-tracking-chat",
      "headline": "Document Conversion API: File, Ad Tracking & Chat Explained",
      "description": "Confused by 'conversion API'? This guide separates document conversion APIs from Meta/TikTok/LinkedIn tracking APIs and conversational AI APIs — with real examples.",
      "url": "https://convertfleet.com/blog/conversion-api-disambiguation-file-ad-tracking-chat",
      "datePublished": "2026-06-11",
      "dateModified": "2026-06-11",
      "author": {
        "@type": "Organization",
        "name": "Convert Team",
        "url": "https://convertfleet.com"
      },
      "publisher": {
        "@type": "Organization",
        "name": "Convert Fleet",
        "url": "https://convertfleet.com",
        "logo": {
          "@type": "ImageObject",
          "url": "https://convertfleet.com/logo.png"
        }
      },
      "image": {
        "@type": "ImageObject",
        "@id": "https://convertfleet.com/blog/images/hero-conversion-api-disambiguation.png",
        "url": "https://convertfleet.com/blog/images/hero-conversion-api-disambiguation.png",
        "caption": "Diagram showing three types of conversion APIs — file conversion, ad tracking, and conversational messaging — separated into distinct swimlanes",
        "contentUrl": "https://convertfleet.com/blog/images/hero-conversion-api-disambiguation.png",
        "width": 1200,
        "height": 675
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://convertfleet.com/blog/conversion-api-disambiguation-file-ad-tracking-chat"
      },
      "keywords": [
        "document conversion api",
        "file conversion api",
        "meta conversion api documentation",
        "linkedin conversion api documentation",
        "snapchat conversion api documentation",
        "twilio conversations api documentation",
        "woocommerce facebook for woocommerce conversions api documentation",
        "pdf conversion api",
        "office to pdf conversion api",
        "rest api for pdf conversion",
        "n8n file conversion",
        "free currency conversion api",
        "currency conversion api documentation",
        "free api for currency conversion",
        "api for currency conversion free"
      ],
      "articleSection": "Developer Guides",
      "wordCount": 2800,
      "inLanguage": "en-US"
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is the best free file conversion API for n8n workflows?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Convert Fleet offers a free tier with no registration required, making it the fastest to test inside an n8n HTTP Request node. For higher volumes, ConvertAPI's second-based credit system is predictable once you have baseline data. Cloudmersive is viable under 800 calls/month but requires a paid subscription beyond that, which makes it poor value for low-volume workflows."
          }
        },
        {
          "@type": "Question",
          "name": "What is a cheap alternative to Cloudmersive for file conversion?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Convert Fleet is the most direct alternative: no monthly subscription, pay-per-use pricing, 177+ formats, and REST endpoints compatible with n8n, Make.com, and any HTTP client. It specifically fills the gap where Cloudmersive's free tier runs out and the paid plan becomes disproportionate to actual call volume."
          }
        },
        {
          "@type": "Question",
          "name": "Is there a pay-per-use file conversion API with no monthly fee?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Convert Fleet charges per conversion call with no monthly floor. This makes it well-suited for automation workflows with variable or seasonal call volume — you pay nothing in idle months and scale linearly with actual usage rather than against a subscription ceiling."
          }
        },
        {
          "@type": "Question",
          "name": "What file conversion APIs work with Make.com and n8n?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Any REST API that accepts multipart/form-data POST requests and returns binary file output works with both platforms. Convert Fleet, ConvertAPI, and Cloudmersive all meet this requirement. In n8n, set Response Format to File in the HTTP Request node. In Make.com, enable Parse Response as binary in the HTTP module configuration."
          }
        },
        {
          "@type": "Question",
          "name": "What is the difference between the Meta Conversions API and a document conversion API?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "They are completely unrelated. The Meta Conversions API is a server-to-server endpoint for sending ad attribution events — purchases, leads, page views — to Meta's advertising platform. It has nothing to do with file formats. A document conversion API converts files between formats (PDF, DOCX, MP4) via REST. The shared word 'conversion' is the entire source of the confusion."
          }
        },
        {
          "@type": "Question",
          "name": "What is the n8n Convert to File node documentation actually for?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The n8n Convert to File node handles in-memory data transforms: JSON to CSV, binary buffer reshaping, or generating files from structured data. It does not convert between document formats (DOCX to PDF), transcode media, or perform OCR. For those tasks, you need an external file conversion API called via the HTTP Request node."
          }
        }
      ]
    },
    {
      "@type": "ImageObject",
      "@id": "https://convertfleet.com/blog/images/hero-conversion-api-disambiguation.png",
      "url": "https://convertfleet.com/blog/images/hero-conversion-api-disambiguation.png",
      "caption": "Diagram showing three types of conversion APIs — file conversion, ad tracking, and conversational messaging — separated into distinct swimlanes",
      "contentUrl": "https://convertfleet.com/blog/images/hero-conversion-api-disambiguation.png",
      "name": "Three Types of Conversion API Explained",
      "description": "Visual map of three unrelated API categories all called conversion API: file and document conversion, server-side ad tracking, and conversational messaging APIs",
      "width": 1200,
      "height": 675
    }
  ]
}