REST API for Programmatic Link Creation

HTMLvault Team·June 22, 2026·4 min read

The Problem: Manual Steps Break Automated Workflows

Your AI assistant just generated a polished HTML proposal. Now what? You copy the output, open HTMLvault, paste it in, configure settings, copy the link, go back to your workflow. Every manual step is friction—and friction kills adoption.

RevOps teams building Clay sequences, marketers wiring Zapier automations, and sales reps working inside Claude or ChatGPT all hit the same wall: the HTML generation is automated, but the sharing still isn't.

The REST API removes that gap. Any tool that can make an HTTP request can create an HTMLvault link and receive a secure, trackable URL in the response.

Who This Is For

RevOps and automation builders who need to programmatically generate personalized content at scale—account-based landing pages, custom pricing sheets, onboarding portals—and distribute unique links without manual intervention.

Sales reps using AI assistants who want Claude, ChatGPT, or Gemini to produce a deliverable and a shareable link in a single prompt, ready to drop into an email.

Developers integrating HTMLvault into internal tools, CRMs, or custom dashboards where HTML output needs a secure, trackable home.

How to Enable API Access

API access requires a Pro or Enterprise plan. Free accounts cannot generate API keys.

Step 1: Generate an API Key

Open Settings → API Keys. Click Create New Key, give it a descriptive name (e.g., "Clay Production" or "Claude MCP"), and copy the key immediately—it won't be shown again.

The API Keys panel in Settings, showing existing keys and the button to create a new one.

Step 2: Authenticate Requests

Include your key in the Authorization header as a Bearer token:

Authorization: Bearer sk_live_your_api_key_here

All requests go to https://api.htmlvault.com/v1/. The API accepts and returns JSON.

Core Endpoints

The API follows REST conventions. Here are the primary operations:

POST /links — Create a new link. Send HTML content in the request body; receive a shareable URL in the response.
GET /links/{id} — Retrieve metadata and settings for an existing link.
PATCH /links/{id} — Update settings (expiry, password, title) without replacing the HTML.
DELETE /links/{id} — Permanently remove a link and its content.

Worked Example: Claude Creates a Proposal Link

Suppose you're using Claude (via MCP or a custom integration) to draft sales proposals. Here's the flow:

The API flow: Claude generates HTML, posts it to HTMLvault, and receives a trackable link.

The request body might look like this:

{
  "html": "<html><body><h1>Proposal for Acme Corp</h1>...</body></html>",
  "title": "Acme Corp Q3 Proposal",
  "expires_in": "7d",
  "password": null,
  "scan_pii": true
}

The response:

{
  "id": "lnk_8xK2mP4vQ",
  "url": "https://view.htmlvault.com/lnk_8xK2mP4vQ",
  "created_at": "2025-01-15T14:32:00Z",
  "expires_at": "2025-01-22T14:32:00Z",
  "pii_scan_status": "clean"
}

Claude can now include that URL directly in its response. The rep copies one link, not a wall of HTML.

Configuration Options

When creating or updating a link, you can set:

expires_in — Duration string (1h, 7d, 30d) or ISO timestamp. Default: 30 days.
password — Optional. Viewers must enter this before seeing content.
scan_pii — Boolean. If true and you've configured BYOK AI keys, HTMLvault scans for PII and secrets before publishing.
custom_domain — Slug of a verified white-label domain. Enterprise only.
tracking_codes — Inject your own analytics snippets (Google Analytics, HubSpot, etc.).

Limits and Caveats

Plan-based rate limits — Pro accounts: 100 requests/minute. Enterprise: configurable. Exceeding limits returns 429 Too Many Requests.
Payload size — Maximum HTML body: 5 MB. For larger files, contact support.
PII scanning requires BYOK — The scan_pii flag only works if you've added your own Anthropic, OpenAI, or Google API key in Settings. HTMLvault doesn't fund AI tokens.
No indexing, ever — Links created via API follow the same security model: never indexed by search engines, zero data retention after expiry.

Why This Matters

For the RevOps lead building a Clay sequence that generates 500 personalized landing pages overnight, the API is the difference between "clever experiment" and "production workflow." For the sales rep who just asked Claude to create a pricing comparison, it's the difference between a polished link in their outbox and a messy HTML blob they have to wrangle manually.

Automation only works when every step is automated. The REST API closes the loop—so the HTML your tools generate actually reaches your prospects, tracked, secured, and ready to drive the next conversation.

Product Featureproduct featureapiintegrationsautomationrest apideveloper tools

REST API: Create and Manage Links Programmatically