canonical: https://jentic.com/apis/theguardian.com/theguardian

# The Guardian Content API

The Guardian's Open Platform Content API provides free access to all content published on theguardian.com. Search for articles, browse sections and tags, retrieve specific content items, and access edition-specific content. Supports filtering by date, section, tag, and more. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically search for content, get a single content item. Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Search for content
- Get a single content item
- List all sections
- Query and filter The Guardian Content API records by parameters
- Monitor The Guardian Content API operational status and events

## Use cases

### CRM Operations

Use the The Guardian Content API to perform crm operations programmatically. The API provides 5 endpoints covering core functionality including search for content, get a single content item, search for tags.

Example prompt: Call GET /search to search for content

### Automated Content Management

Automate content operations by combining multiple The Guardian Content API endpoints. Agents can get a single content item and then search for tags in a single workflow.

Example prompt: Call GET /{contentId} to get a single content item, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call The Guardian Content API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'search for content', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /search | Search for content |
| GET | /{contentId} | Get a single content item |
| GET | /tags | Search for tags |
| GET | /sections | List all sections |
| GET | /editions | List all editions |

## Key resources

- **Content** — Search and retrieve Guardian content items
- **Tags** — Browse and search Guardian tags (keywords, series, contributors, etc.)
- **Sections** — Browse Guardian sections
- **Editions** — Browse Guardian editions (UK, US, AU, International, Europe)

## Why Jentic

- **Setup:** Wiring The Guardian Content API by hand means passing your API key against content.guardianapis.com and handling each search and content endpoint yourself. Through Jentic you install once, import The Guardian Content API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Guardian Content API is read-only and puts the content id in the URL path (/{contentId}), so a rule can pin your agent to reading one item. You choose the operations it may call, so it only reaches the endpoints you include, such as search or fetching a single article.
- **Credential handling:** Your Guardian 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.
- **Discovery method:** Agents search Jentic by intent such as 'search for articles on a topic' or 'list content tags', and Jentic returns the matching Guardian operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the The Guardian Content API use?

The The Guardian Content API uses an API key passed in the `api-key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I search for content with the The Guardian Content API?

Yes. Use the GET /search endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the The Guardian Content API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I search for content through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search for content'. Jentic returns the matching The Guardian Content API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the The Guardian Content API have?

The The Guardian Content API exposes 5 endpoints covering content, tags, sections operations.

### Can I limit what my agent is allowed to do with the Guardian Content API?

Yes. Because Jentic One is self-hosted, your own rules decide which Guardian operations the agent may call, so you can allow only GET /search and GET /{contentId} while blocking the rest. Since the API is read-only and puts the content id in the URL path, you can pin the agent to fetching a single article or restrict it to searching by section or tag. Your Guardian API key stays with your instance and is injected only when an allowed operation runs.