▣ DATA EXTRACTION · MARKETING

Extract Metadata From URL API

What it does

URL Metadata Extractor reads a webpage URL and returns the page metadata it can extract. Use it when you need to inspect links, index page information, or build a preview workflow without fetching and parsing HTML yourself.

Send a single URL with the GET endpoint, or submit an array of URLs in the POST batch endpoint under body.urls. The batch method is useful when you need to process multiple pages at once from a crawl, import, or enrichment job.

Use URL Metadata Extractor when your app needs page-level metadata for search indexing, content cataloging, link previews, or automated QA across a set of webpages. It is a fit for pipelines that collect metadata from many URLs and hand the results to downstream storage, analysis, or review systems.

The service returns metadata extracted from the provided URLs. Because the API schemas do not expose fixed response fields here, plan to consume the structured result as returned by the service.

▣ ENDPOINT 01 / 02

GET

Extract Metadata from a URL

https://api.eu.apyverse.com/namastesumalya/extract-metadata-from-url-api

QUICKSTART

GUIDE

Quickstart

Fetch metadata from a URL with a simple GET request.

curl -X GET "https://api.eu.apyverse.com/namastesumalya/extract-metadata-from-url-api?url=https://apyhub.com" \
  -H "apy-token: $APY_TOKEN"

What you'll get back

Returns a JSON object with these top-level string fields: url, title, author, platform, reading_time, publication_date, and publication_name.

{
  "url": "https://example.com/article",
  "title": "Understanding AI in Modern Applications",
  "author": "John Doe",
  "platform": "Medium",
  "reading_time": "4 min",
  "publication_date": "2025-02-10",
  "publication_name": "Medium"
}

TRY ITLIVE · 300 ATOMS

API key

Loading your default key…

The full key is used to call the gateway and stays in this tab — never sent to orbit or saved.

About this endpoint

What it does

Extracts metadata from the URL you provide and returns it in a JSON object. The response may include the source URL along with common metadata fields such as title, author, platform, reading time, publication date, and publication name.

Query Parameter(s)

Attribute	Type	Mandatory	Description
url	String	Yes	The URL to extract metadata from.

Response

Returns a JSON object with url, title, author, platform, reading_time, publication_date, and publication_name string fields.

Parameter	Type	Mandatory	Description
url	String	No	The source URL that was processed.
title	String	No	The extracted title.
author	String	No	The extracted author.
platform	String	No	The platform associated with the URL.
reading_time	String	No	The estimated reading time.
publication_date	String	No	The publication date.
publication_name	String	No	The publication name.

Query parameters

Name

Type

Description

urlREQUIRED

string

—

▣ ENDPOINT 02 / 02

POST

Batch Extract Metadata from Multiple URLs

https://api.eu.apyverse.com/namastesumalya/extract-metadata-from-url-api

QUICKSTART

GUIDE

Quickstart

Send one or more URLs in a JSON body to extract their metadata.

curl -X POST "https://api.eu.apyverse.com/namastesumalya/extract-metadata-from-url-api" \
  -H "apy-token: $APY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://example.com", "https://apyhub.com/pricing"]}'

What you'll get back

Returns a JSON object with a data array. Each item in data is an object describing one URL, with fields like url, title, author, platform, reading_time, publication_date, and publication_name.

{
  "data": [
    {
      "url": "https://example.com/article",
      "title": "Understanding AI in Modern Applications",
      "author": "John Doe",
      "platform": "Medium",
      "reading_time": "4 min",
      "publication_date": "2025-02-10",
      "publication_name": "Medium"
    }
  ]
}

TRY ITLIVE · 500 ATOMS

API key

Loading your default key…

The full key is used to call the gateway and stays in this tab — never sent to orbit or saved.

About this endpoint

What it does

Submits a batch request to extract metadata from multiple URLs provided in the request body. The success response schema is not yet defined, so the exact response payload is not documented here.

Request Body

Parameter	Type	Mandatory	Description
urls	String Array	Yes	The URLs to process in a single batch.

Body

Name

Type

Description

bodyOPTIONAL

object

—

▣ COMMON ERRORS

Errors any endpoint can return

400bad_request

Required parameter missing or malformed body.

401unauthorized

API key missing, revoked, or not authorized for this service.

429rate_limited

Your plan's per-second rate exceeded. Retry with exponential backoff.

503upstream_busy

Backend temporarily unavailable. Try again in a few seconds.