How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Dailyhunt Content Fetch API

Paginated retrieval of the content cards inside a channel, plus keyword search.

Dailyhunt Content Fetch API is one of 8 APIs that Dailyhunt publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content Fetch. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.3.

Requests are made against 3 base URLs: http://feed.dailyhunt.in, http://qa-news.newshunt.com, http://track.dailyhunt.in.

2 operations 2 paths 4 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.3
Base URL
http://feed.dailyhunt.in/api/v2/syndication
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Dailyhunt Content Fetch API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). An API key is passed in the header as Signature (RequestSignature). By default, every request must be authenticated.

  • ApiKeyAuth — The partner API key issued by Dailyhunt at onboarding, sent as key= .
  • RequestSignature — Base64-encoded HMAC-SHA1 of the signature base string, computed with the partner secret key. The signature base string is the URL-encoded request query paramet…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Content Fetch 2

Paginated retrieval of the content cards inside a channel, plus keyword search.

GET
/api/v2/syndication/items
Fetch content cards from a channel
fetchItems 10 params → 200401403500
GET
/api/v2/syndication/search
Search content
searchContent 7 params → 200401403500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Item (24 properties), Thumbnail (3 properties), ShareInfo (2 properties), ItemListResponse (2 properties). Each schema is shown below with its type and property counts.

Thumbnail
object
3 properties
ItemListResponse
object
2 properties
ShareInfo
object
2 properties
Item
object
A content card. Content types are STORY, VIDEO, PHOTO, ASTROLOGY, VHMEME, BANNER, QUESTIONMULTICHOICES and HTML.
24 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dailyhunt-content-fetch-api-openapi.yml Raw ↑

Other APIs Dailyhunt publishes across the network.

Dailyhunt Catalog API
Dailyhunt Channels API
Dailyhunt Cricket API
Dailyhunt Feedback API
Dailyhunt Languages API
Dailyhunt Products API
Dailyhunt Tracking API
Where this information came from

This is an independent, third-party profile of Dailyhunt Content Fetch API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.