Developer Docs

Public documentation for the PressWire India News Provider API

Understand the onboarding flow, authentication model, endpoint behavior, filters, response format, access controls, and implementation path before you integrate.

Register as News Provider View Code Examples Program Overview

API At a Glance

GET https://www.presswireindia.com/api/v1/news/releases
  • Versioned partner API
  • Published-only release delivery
  • Header-based authentication
  • Category, search, and sync filters

Built For

Who should use this API

Website

Structured press release intake for editorial, publishing, search, and distribution workflows.

App

Structured press release intake for editorial, publishing, search, and distribution workflows.

Print

Structured press release intake for editorial, publishing, search, and distribution workflows.

Tv

Structured press release intake for editorial, publishing, search, and distribution workflows.

Radio

Structured press release intake for editorial, publishing, search, and distribution workflows.

Aggregator

Structured press release intake for editorial, publishing, search, and distribution workflows.

Onboarding Flow

How access works from signup to live API use

1

Register

Submit your organization, website, domain, official email, country, and provider type.

2

Verify Domain

Add the provided DNS TXT record to prove ownership of the claimed website domain.

3

Admin Approval

PressWire India reviews the provider before activating API access and traffic policy.

4

Generate API Key

Once approved and verified, the provider creates an API key and starts server-side integration.

Authentication

Required request headers

Every request must send the provider ID and API key in HTTP headers.

X-Provider-Id: YOUR_PROVIDER_ID
Authorization: ApiKey YOUR_API_KEY
Accept: application/json

Endpoint

Primary feed endpoint

GET https://www.presswireindia.com/api/v1/news/releases
Parameter Purpose
category_id Optional category filter.
q Optional search query.
limit Optional result limit from 1 to 60.
since Optional ISO-8601 datetime for incremental sync.
cursor Optional pagination token from the previous response.

Filter Logic

  • No filters returns the latest published press releases.
  • category_id narrows the result to one category.
  • q searches the release dataset.
  • since supports incremental syncing.
  • cursor continues pagination safely.

Response Model

What a success response includes

  • meta.provider_id to identify the authenticated partner context
  • meta.count and meta.limit for result bookkeeping
  • meta.next_cursor for pagination continuation
  • items array containing release fields, category, tags, URLs, and timestamps

Errors

Standard error structure

{
  "error": {
    "code": "provider_disabled",
    "message": "Provider account is inactive or pending approval.",
    "status": 403
  }
}
  • invalid_api_key
  • provider_disabled
  • ip_not_allowed
  • access_denied
  • invalid_request

Security and Policy

  • API keys must never be sent in query strings.
  • Providers may be restricted by IP allowlist.
  • Inactive or banned providers are blocked even if a key exists.
  • Rate limits are configurable per provider.
  • Only published press releases are exposed.

Implementation Flow

  • Authenticate using headers on every request.
  • Pull the latest batch with or without filters.
  • Store next_cursor or since in your system.
  • Fetch incrementally on a schedule that respects your quota.
  • Display or process only after your editorial logic runs.

Next Step

Move from docs to implementation

Review the code examples, register your platform, complete DNS verification, and then generate a live API key from the News Provider panel.

Open Code Examples Go to Signup