Dailyhunt Authentication

generated: '2026-08-04'
method: searched
source: openapi/dailyhunt-content-syndication-openapi.yml, openapi/dailyhunt-shopping-catalog-openapi.yml
docs: https://api-syndication.dailyhunt.in/
summary:
  types:
  - apiKey
  api_key_in:
  - header
  - body
  oauth2_flows: []
  self_service: false
  provisioning: >-
    Credentials are not self-service. Dailyhunt provisions an API Key, a Secret Key and a Partner
    Code during partner onboarding and shares them over email. The E-Commerce Shopping Catalog API
    requires the vendor to be registered first and issues a vendor access_token.
schemes:
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: Authorization
  format: 'key=<API Key>'
  description: >-
    The partner API key issued by Dailyhunt at onboarding, sent on every Content Syndication call in
    the Authorization header with the literal prefix `key=`.
  sources:
  - openapi/dailyhunt-content-syndication-openapi.yml
  docs: https://api-syndication.dailyhunt.in/
- name: RequestSignature
  type: apiKey
  in: header
  parameter: Signature
  algorithm: HMAC-SHA1
  encoding: base64
  description: >-
    Every Content Syndication request additionally carries a request signature. The signature base
    string is built by appending a `ts` timestamp query parameter, URL-encoding every parameter key
    and value, sorting the parameters lexicographically on the encoded key, joining them as
    `key=value` pairs, and appending the uppercased HTTP method. That string is signed with the
    partner Secret Key using HMAC-SHA1 and Base64-encoded into the `Signature` header. Dailyhunt
    publishes worked JavaScript and Java reference implementations in the Partner Integration
    Reference.
  sources:
  - openapi/dailyhunt-content-syndication-openapi.yml
  docs: https://api-syndication.dailyhunt.in/
- name: VendorAccessToken
  type: apiKey
  in: body
  parameter: access_token
  description: >-
    The E-Commerce Shopping Catalog API authenticates with a vendor access_token passed as a field in
    the JSON request body of every catalog and batch call. The vendor must already be registered in
    the Dailyhunt system.
  sources:
  - openapi/dailyhunt-shopping-catalog-openapi.yml
  docs: https://developer.dailyhunt.in/ads/docs/shopping-catalog/
identity:
  partner_user_id:
    parameter: puid
    required: true
    description: >-
      A partner-supplied unique identifier for the end user consuming Dailyhunt content (for example
      a device identifier). Required on every Content Syndication call. Dailyhunt maps it to an
      internal user id to build a personalization profile.
  session_cookie:
    name: dhFeedV1
    description: >-
      Dailyhunt returns a per-user dhFeedV1 cookie on the first API response. The partner must
      persist it per user and replay it on subsequent calls; Dailyhunt regenerates it if missing or
      expired and rejects requests carrying an invalid one. It avoids repeated puid-to-internal-id
      lookups.
    ttl: one month initially (Dailyhunt notes this may change)
notes:
- No OAuth 2.0 or OpenID Connect surface is published; there is no scope model, so no scopes/
  artifact is emitted for this provider.
- No self-service developer signup exists for the Content Syndication API. The only self-service
  signup on the estate is the Dailyhunt Direct advertising console at https://direct.dailyhunt.in/login.
x-evidence:
  fetched: '2026-08-04'
  urls:
  - {url: 'https://api-syndication.dailyhunt.in/', http_status: 200}
  - {url: 'https://developer.dailyhunt.in/ads/docs/shopping-catalog/', http_status: 200}