Pocket API

Name: Pocket API
Brand: Pocket API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityNote TakingapiKey7 EndpointsREST

For Agents

Save URLs to a user's Pocket queue, retrieve saved items by tag or state, and apply batch tag and archive operations through OAuth-scoped access tokens.

Connect the Pocket API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pocket 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Pocket API.

Add a URL with optional tags and title to the user's Pocket queue

Retrieve saved items filtered by state, tag, content type, or modified-since timestamp

Apply batch actions to archive, favourite, delete, or retag many items at once

Run the OAuth request-token and access-token flow to authorise a new user

GET STARTED

Start building with Pocket API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Pocket API, keeping it validated and agent-ready. Pocket is a read-it-later service that lets users save articles, videos, and links to a personal queue for offline reading and later review. The v3 HTTP API exposes seven endpoints covering item ingestion, batch modifications, retrieval with filters and tags, OAuth handshake, tag listing, and account-level statistics. It is the canonical integration surface for browser extensions, recommendation pipelines, and reading-list automation that needs a stable, long-lived saved-item store.

Use Cases

Patterns agents use Pocket API for, with concrete tasks.

★ Read-later pipeline from chat agents

Knowledge workers paste links into a chat agent and ask it to 'save this for later'. The agent calls Pocket's add endpoint with the URL and a context-derived tag, building a structured personal reading queue without manual triage. Retrieval later is one search-by-tag away.

Save https://example.com/long-read to Pocket with tags 'research' and 'ai-agents' and confirm the item id

Tag-driven content recommender

Build a weekly digest by retrieving Pocket items with a specific tag added since the last digest run, summarising each, and emailing the result. The /get endpoint supports tag and since filters, so the digest job pulls only the new items rather than re-processing the full archive.

Retrieve all Pocket items with tag 'ml-papers' added since 2026-06-01 and produce a summarised digest

Archive cleanup at scale

Power users accumulate thousands of saved items. The /send endpoint accepts a batch of actions in one request, so an agent can archive everything older than a threshold or retag a set of items without making a call per item. This is meaningfully cheaper than walking the queue one item at a time.

Archive all unread Pocket items older than 90 days in a single batch /send call

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for pocket api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/add

Save a URL to the user's queue

POST

/get

Retrieve saved items with filters

POST

/send

Apply batch actions to many items

POST

/oauth/request

Request an OAuth request token

POST

/oauth/authorize

Exchange request token for access token

POST

/tags/get

List all tags applied across items

POST

/add

Save a URL to the user's queue

POST

/get

Retrieve saved items with filters

POST

/send

Apply batch actions to many items

POST

/oauth/request

Request an OAuth request token

POST

/oauth/authorize

Exchange request token for access token

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pocket's consumer_key and per-user access_token are stored encrypted in the Jentic vault. Agents receive scoped references and the raw token strings never enter prompt context.

Intent-based discovery

Agents search by intent such as 'save url to read later' and Jentic returns the matching Pocket /add operation along with its input schema.

Time to first call

Direct Pocket integration: 1-2 days for the OAuth dance and batch-send semantics. Through Jentic: under an hour to search, load, and execute.

FAQs

Specific to using Pocket API through Jentic.

Why is there no official OpenAPI spec for Pocket API?

Pocket does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pocket API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Pocket API use?

Pocket uses a consumer_key plus a per-user access_token sent in the request body. The OAuth handshake at /oauth/request and /oauth/authorize mints the access_token. Through Jentic the consumer_key and access_token are vaulted and injected at execution time.

Can I save a URL to Pocket through the API?

Yes. POST /add with the URL and optional tags or title creates a new saved item in the user's queue. The response returns the canonical item identifier you can later use with /send for batch operations.

What are the rate limits for the Pocket API?

The OpenAPI spec does not encode explicit rate limits, but Pocket historically applies per-consumer-key and per-user-token thresholds. Use the /send batch endpoint for bulk modifications instead of looping /add or /modify, which keeps you well under the limits.

How do I retrieve saved items filtered by tag through Jentic?

Search Jentic for 'get pocket items by tag', load the POST /get schema, then execute with the tag and optional since timestamp. Jentic injects the consumer_key and access_token automatically.

Can I run multiple actions in one call?

Yes. POST /send accepts an actions array where each element is an archive, favourite, delete, tag-add, or tag-remove action. This is the supported way to perform bulk maintenance without flooding the per-item endpoints.

Is the Pocket API free?

Pocket's API has historically been free for developers with a registered consumer_key, though Pocket's product status has shifted recently — check getpocket.com for current availability and any successor service before building production integrations.

Pocket API

Connect the Pocket API to your agent

Capabilities

Start building with Pocket API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs