PR.co API

Name: PR.co API
Brand: PR.co API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey23 EndpointsREST

For Agents

Retrieve press releases, media clippings, events, media kits, and spokesperson contacts from PR.co pressrooms for PR monitoring and content syndication.

Install Jentic One Beta

Connect the PR.co API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PR.co API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpr.co%2Fpr" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpr.co%2Fpr" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PR.co API.

Retrieve published and archived press releases with full body content and tags

Access media clippings that track press coverage with publication details

Query upcoming and past PR events with location and date information

GET STARTED

Start building with PR.co API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PR.co API for, with concrete tasks.

★ Press Release Syndication

Pull published press releases from PR.co and syndicate them to company websites, social media channels, or newsletter platforms. The API returns full press release content including title, body, tags, publication date, and URL, enabling automated distribution workflows that publish announcements across multiple channels simultaneously.

Fetch the latest press releases via GET /press_releases.json, filter for those published in the last 7 days, and extract title, summary, and URL for distribution

Media Coverage Monitoring

Monitor media clippings to track press coverage for a brand or product launch. The clippings endpoint returns publication name, article title, URL, and publication date for each media mention, enabling PR teams to measure coverage volume and identify which outlets are covering their announcements.

Retrieve all clippings via GET /clippings.json and compile a report showing publication name, date, and URL for each media mention in the current quarter

Media Kit Distribution

Provide journalists and partners with programmatic access to media kit assets including brand logos, product images, videos, and press documents. The API serves image URLs with dimensions and document files with metadata, enabling self-service media portals that stay current with the latest brand assets.

List media kits via GET /media_kits.json, then retrieve images via GET /images.json and documents via GET /documents.json to compile a complete asset package

AI Agent PR Content Access via Jentic

Enable AI agents to access pressroom content through Jentic for answering press inquiries, generating coverage reports, or populating communications dashboards. Agents discover the relevant PR.co operation via intent search, load the schema, and execute calls to retrieve press releases, clippings, or contacts.

Search Jentic for 'retrieve press releases from pressroom', load the PR.co operation schema, and execute GET /press_releases.json to return the latest announcements

Key Endpoints

23 endpoints — jentic publishes the only available openapi specification for pr.

METHOD

PATH

DESCRIPTION

GET

/press_releases.json

List all published press releases

GET

/press_releases/{id}.json

Get a single press release by ID

GET

/clippings.json

List media clippings

GET

/events.json

List PR events

GET

/media_kits.json

List media kits

GET

/search/all.json

Full-text search across all content

GET

/pr_contacts.json

List spokesperson contacts

GET

/timeline.json

Get pressroom activity timeline

GET

/press_releases.json

List all published press releases

GET

/press_releases/{id}.json

Get a single press release by ID

GET

/clippings.json

List media clippings

GET

/events.json

List PR events

GET

/media_kits.json

List media kits

GET

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PR.co API by hand means setting the X-API-Key header, substituting your pressroom id into the api.pr.co/v1/pressrooms/{pressroom_id} base URL, and paging content endpoints yourself. Through Jentic you install once, import the PR.co API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

PR.co scopes every path to a pressroom id carried in the base URL and takes item ids in the path (/press_releases/{id}.json), so a rule can pin your agent to one pressroom's content and nothing else. This spec exposes only read operations, so no publishing or edit action is included.

Credential isolation

Your PR.co API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'retrieve press releases from a pressroom' or 'list media kits', and Jentic returns the matching PR.co operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PR.co API through Jentic.

Why is there no official OpenAPI spec for PR.co API?

PR.co does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PR.co API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the PR.co API use?

The PR.co API uses API key authentication passed in the X-API-Key header. Each request must include a valid API key associated with your PR.co pressroom. Through Jentic, this key is stored encrypted in the credential vault and agents access it without handling raw credentials.

Can I search across all pressroom content with the PR.co API?

Yes. The GET /search/all.json endpoint accepts a q query parameter and searches across press releases, clippings, events, and media kits simultaneously. For targeted searches, use GET /search/press_releases.json to search only press releases.

Is the PR.co API read-only?

Yes. All 23 endpoints in this specification are read-only GET requests. The API is designed for content retrieval and syndication, not for creating or editing pressroom content. Content management is handled through the PR.co web interface.

How do I retrieve press releases through Jentic?

Install the Jentic SDK with pip install jentic, then search for 'list press releases from pressroom'. Jentic returns the PR.co GET /press_releases.json operation with its schema. Execute the call to retrieve all published press releases for your pressroom.

What media asset types does the PR.co API support?

The API provides access to documents (with file type and size), images (with dimensions and thumbnail URLs), and videos (with duration and thumbnail URLs). These are accessible via /documents.json, /images.json, and /videos.json respectively, or bundled within media kits via /media_kits.json.

Can I limit what my agent is allowed to do with the PR.co API?

Yes. Because you run Jentic One yourself, your own rules decide which PR.co operations and credentials your agent can use. Since every path is scoped to a pressroom id in the base URL and item ids sit in the path (for example /press_releases/{id}.json), you can pin the agent to a single pressroom's content and nothing else. This specification exposes only read operations such as GET /press_releases.json, GET /clippings.json, and GET /search/all.json, so no publishing or editing action is available to the agent.