Link Preview API

Product Introduction

1. Definition: The Exabase Link Preview API is a specialized, production-ready web service that programmatically extracts and returns structured metadata (Open Graph tags, HTML meta tags, and page information) from any public URL. It falls under the technical categories of web scraping APIs, metadata extraction services, and developer tools for content enrichment.
2. Core Value Proposition: It exists to eliminate the complex, maintenance-heavy engineering required to generate rich link previews (like those seen in Slack or Twitter) by providing a single, reliable API call. Its primary value is offering a completely free link preview API with JavaScript rendering, dedicated handling for popular websites, and built-in image validation, enabling developers to ship professional features faster.

Main Features

1. JavaScript Rendering & Headless Browser Execution: Unlike basic HTTP scrapers, this API fetches and fully renders web pages, including those built with modern frameworks like React, Next.js, or Vue.js. It executes client-side JavaScript to ensure accurate extraction of Open Graph tags and page titles that are dynamically loaded. This is achieved through a managed headless browser infrastructure, removing the need for developers to maintain Puppeteer or Playwright instances.
2. Content Provider Integrations & Anti-Bot Evasion: The service includes dedicated, optimized parsers for high-traffic sites like YouTube, Amazon, Twitter, Airbnb, SoundCloud, The New York Times, Vimeo, and Giphy. These integrations ensure reliable, high-quality previews. Furthermore, the API handles proxy rotation, browser fingerprinting, and retry logic automatically to achieve a >95% success rate against sites that employ anti-scraping measures.
3. Comprehensive Metadata & Image Validation: The API returns a complete JSON object containing not just basic title, description, and image URL, but also the canonical URL, site name, locale, and detailed media analytics. Crucially, it validates images and favicons, returning their exact pixel dimensions (image_x, image_y), file size in bytes (image_size), and MIME type (image_type), allowing developers to programmatically filter out unsuitable images without a secondary fetch.
4. CORS Support & Built-in Caching: The API is configured with Cross-Origin Resource Sharing (CORS) headers, allowing it to be called directly from frontend web applications during prototyping. For production, backend integration is recommended. It also features an automatic caching layer, where popular URLs are served from cache for instant response, and first-time fetches are cached for up to 24 hours to optimize performance and reduce load on target sites.

Problems Solved

1. Pain Point: Manually building and maintaining a reliable link preview system is a significant engineering burden. It requires handling headless browsers, managing timeouts and retries, parsing inconsistent HTML/OG tags, evading bot blocks, implementing caching, and validating images—a process prone to breakage and high ongoing maintenance.
2. Target Audience: This API serves Full-Stack and Frontend Developers building chat applications, social platforms, or CMS tools; Product Managers needing to implement rich media features without extensive dev cycles; Content Managers and SEO Specialists who require automated audits of Open Graph tags across websites.
3. Use Cases:
   • Chat/Messaging Apps: Automatically render rich link cards when users paste URLs into chat interfaces (Slack, Discord, iMessage clones).
   • Content Management Systems (CMS): Allow editors to paste a URL and have the system auto-generate an embedded preview card with title, image, and description for blog posts or articles.
   • Bookmarking & Read-Later Services: Auto-populate saved links with correct titles, descriptions, and thumbnails upon user submission.
   • Social Media Scheduling Tools: Preview exactly how a link will appear (including image dimensions) on platforms like Twitter or Facebook before publishing.
   • SEO Audit Tools: Programmatically check client websites for the presence, correctness, and consistency of Open Graph metadata versus standard HTML title tags.

Unique Advantages

1. Differentiation vs. Building In-House: Compared to an internal build with Puppeteer, Exabase removes all infrastructure complexity, ongoing maintenance, and scaling concerns, turning a multi-week project into a single API integration. Versus competitors like OpenGraph.io, Exabase offers a significantly more generous free tier (20,000 monthly previews vs. typically 1,000), includes JavaScript rendering as standard, and provides detailed image analytics.
2. Key Innovation – The Integrated Exabase Stack: The Link Preview API is not a standalone tool but part of a broader data extraction ecosystem. Its key innovation is seamless integration with Exabase's Extract API. When a use case evolves from needing just link preview metadata to requiring full-page content extraction (for RAG pipelines, deep search, or analysis), developers can use the same API key and platform to access structured text, chunks, and data from PDFs, images, and entire websites, creating a unified data-ingestion workflow.

Frequently Asked Questions (FAQ)

1. Is the Exabase Link Preview API really free? Yes, the API offers a completely free tier allowing up to 20,000 link preview requests per month. Beyond this threshold, usage incurs a nominal per-request charge, making it cost-effective for both prototyping and high-scale production applications.
2. How does this API handle websites that require JavaScript to load content? The Exabase Link Preview API employs a full headless browser rendering engine. It fetches the URL and executes all client-side JavaScript, just like a modern web browser, before extracting metadata. This ensures accurate data from Single Page Applications (SPAs) built with React, Angular, Vue.js, and Next.js.
3. Can I use the Link Preview API directly from my React or Vue.js frontend application? While the API supports CORS and can be called from client-side code for prototyping, exposing your API key in the browser is a security risk. For production applications, it is strongly recommended to call the API from your own backend server, which then forwards the sanitized data to your frontend.
4. What happens if a website has no Open Graph tags? The API implements a robust fallback strategy. It will first parse all Open Graph (og:) tags. If these are missing or incomplete, it falls back to standard HTML metadata, such as the <title> tag, <meta name="description">, and the first relevant <img> tag in the document body to generate a comprehensive preview.
5. What is the difference between the Link Preview API and the Exabase Extract API? The Link Preview API is designed for retrieving surface-level metadata (title, description, image, URL) to build preview cards. The Extract API is a more powerful tool for full-content extraction, returning the entire structured text of a webpage, PDF, or image broken into searchable chunks, suitable for feeding into RAG systems or knowledge bases. They are complementary tools within the same platform.