apiPulse.app
This is a live demo. Register to save subscriptions and get email notifications.

Historical changes

2358 entries from demo-selected APIs

Add API
10-17-2026
Cloudflare

Workers, Cloudflare CLI - Test Cron Triggers with Local Explorer

Local Explorer can now send one-off Cron Trigger invocations to a Worker's scheduled() handler during local development. This removes the need to construct request URLs when testing handler behavior. Start your local development server with cf dev, wrangler dev, or the Cloudflare Vite plugin. Open /cdn-cgi/local/explorer on the server URL and select Cron Triggers. The browser interface supports the following tasks: Invoke configured cron expressions Build ad hoc expressions Set reusable scheduled times Inspect outcomes and noRetry() status Ad hoc triggers and scheduled time presets stay in your browser. They do not change cloudflare.config.ts, your Wrangler configuration, or deployed Cron Triggers. Local development does not run cron schedules automatically. Full logs and traces are available in the development session that owns the Worker when that session has Observability turned on. The following example uses port 8787. Replace it with your development server port, such as 5173 for Vite. The Local Explorer API exposes the same operation for tools and AI agents. The request targets an exact Worker name and accepts a cron expression and optional scheduled time: curl -X POST \ "http://localhost:8787/cdn-cgi/local/explorer/api/local/scheduled?worker=my-worker" \ -H "Content-Type: application/json" \ --data '{"cron":"0 * * * *","scheduled_time":1745856238000}' For more details, refer to Test Cron Triggers with Local Explorer.

Source
10-16-2026
Claude

2.1.302

Added Added CLAUDE_CODE_AUTO_MODE_MODEL to choose the model the client-side auto mode classifier uses; it does not change the model for server-side auto mode Added an Idle compaction row to /config for turning idle compaction off or back on; the notices shown after an idle compaction now say how to turn it off Added a notice to /design-sync and /design-login that standalone Claude Design (claude.ai/design) closes by December 14, 2026 [Cloud sessions] Added a banner on a routine's page that says why its last run didn't start, such as your organization reaching its limit on concurrent cloud sessions Changed Changed claude -p and Agent SDK sessions with no permission mode to start in default mode on third-party providers, with telemetry off or on a fresh install; --permission-mode auto keeps auto Changed fork subagents (subagent_type: "fork") to be on by default in claude -p, the Agent SDK, the desktop app and VS Code, as they already are in the terminal; CLAUDE_CODE_FORK_SUBAGENT=0 turns them off, and claude mcp serve never offers them Changed the desktop app and VS Code to always run the main conversation's subagents in the background, as the terminal does, rather than let Claude choose; a subagent's own Agent calls in claude -p, the Agent SDK, the desktop app and VS Code now run in the foreground by default Changed the ← for agents footer hint to hide 10 seconds after a session opens; the count of agents waiting on you still shows Changed where the Claude in Chrome instructions sit in the system prompt so that new conversations can read them from the shared prompt cache Changed prompt and agent hooks so that at most 12 of one event run at a time; the rest wait their turn Changed the message shown when your organization's policy turns off /feedback: it now points to GitHub issues instead of an organization admin [Claude Tag] Changed Claude Tag admin settings to organize Claude's access into four tabs: Bundles, Connectors, Skills and plugins, and Channels [Claude Tag] Changed the Roles page in organization settings to group the roles created for Claude Tag channel managers in a collapsed section below your organization's own roles

Source
10-16-2026
Atlassian

[Announcement] Global Apps EAP

EARLY ACCESS: Forge Global Apps We are ready to kick off the Forge Global Apps Early Access Program (EAP). Forge Global Apps are installed in the platform and can optionally link to one or more Atlassian apps.What's changingInstallation into unit instead of an Atlassian app workspaceApps can work across sites in a unitNo required Atlassian app link What you need to do Sign up for the EAP: submit a request  https://ecosystem.atlassian.net/servicedesk/customer/portal/1040/create/18611  and we will get in touch with instructions soon

Source
10-16-2026
Atlassian

[Announcement] Atlassian cloud will start using new IP address ranges as we expand our cloud infrastructure

What's changing From January 1, 2027, Atlassian cloud will add new IP address ranges as we expand our cloud infrastructure.The new ranges are in addition to our existing ones.The new ranges are:New range: 131.162.88.0/21Requests to Atlassian (browsers and your clients calling Atlassian APIs): 131.162.88.0/23Requests from Atlassian (webhooks, Connect lifecycle calls, and other requests from Atlassian to your app): 131.162.90.0/23What you need to do If your app, remote backend, or integration allowlists Atlassian IP addresses, you must add these ranges before January 1, 2027, to avoid service interruptions.These ranges are already included in our official IP range list (viewer tool). If you automate your allowlist updates from this file, no further action is required. For more details, see our documentation on IP addresses and domains for Atlassian cloud apps.

Source
10-16-2026
Cloudflare

AI Search - AI Search keyword search supports Japanese, Chinese, and Korean queries

AI Search keyword search with the trigram tokenizer now matches Japanese, Chinese, and Korean queries, including full natural-language questions such as 経費精算の締め日はいつですか？. Previously, a query without spaces was treated as a single exact phrase and usually returned no keyword results. The porter tokenizer does not work well for these languages. If your content is in Japanese, Chinese, or Korean, set keyword_tokenizer to trigram. Changing the tokenizer triggers a full reindex. Refer to Keyword search for tokenizer details.

Source
10-16-2026
Cloudflare

Cloudflare Tunnel, Cloudflare Tunnel for SASE, Cloudflare Mesh, Cloudflare One - 50,000 routes per account and Tunnels for Platforms

Two changes make it easier to run Cloudflare Tunnel at scale. 50,000 routes per account by default The default limit for routes is now 50,000 per account, up from 1,000. This limit covers CIDR routes and hostname routes for Cloudflare Tunnel and Cloudflare Mesh. The new limit applies to every account automatically, with no action required. Published applications (public hostnames) are not routes and are not affected by this limit. Each tunnel supports roughly 5,000–10,000 published applications, depending on the size of its configuration. For details, refer to Published application limits. Tunnels for Platforms Every account includes 1,000 tunnels. With Tunnels for Platforms, you can now run more than 1,000 tunnels in a single account — for example, one tunnel per device, per end customer, or per development environment. To buy additional tunnels, go to Networking > Tunnels and select Buy more tunnels in the Usage card. Additional tunnels are billed at $4.50 per tunnel per month. Enterprise customers can contact their account team for committed or usage-based pricing. Go to Tunnels ↗ For pricing, limits, and best practices for managing large tunnel fleets, refer to Tunnels for Platforms.

Source
10-16-2026
Cloudflare

Workers, Cloudflare CLI - Search Cloudflare documentation with the Cloudflare CLI

Cloudflare CLI 1.0.0-beta.16 includes cf docs search, so you and your coding agent can find Cloudflare documentation without leaving the terminal. Search for guides, tutorials, and examples across Cloudflare products. To install or update to the latest release: if (!customElements.get("nb-pm-restore")) { customElements.define( "nb-pm-restore", class extends HTMLElement { connectedCallback() { const card = this.closest("[data-nb-pm]"); if (!card) return; let saved; try { saved = sessionStorage.getItem("ui-pm-tab"); } catch { return; } if (!saved) return; const tabs = card.querySelectorAll("[data-nb-pm-tab]"); let idx = -1; tabs.forEach(function (t, i) { if (t.textContent.trim() === saved) idx = i; }); if (idx < 1) return; tabs.forEach(function (t, i) { t.setAttribute("aria-selected", String(i === idx)); }); card.querySelectorAll("[data-nb-pm-panel]").forEach(function (p, i) { p.hidden = i !== idx; }); } }, ); } npmyarnpnpmbunnpm install --global cf@latestyarn global add cf@latestpnpm add --global cf@latestbun add --global cf@latest Describe what you want to do, or ask a question: cf docs search "proxy a DNS record" cf docs search "rate limit requests with WAF" cf docs search "schedule a worker" The command searches live Cloudflare documentation and returns up to five ranked JSON results. Each result includes a title, description, and documentation URL. An Internet connection is required. Agents can parse the results and fetch a complete page as Markdown. For example, use jq to select the first result, then request its URL with the Accept: text/markdown header: url=$(cf docs search "proxy a DNS record" | jq -r '.[0].url') curl -H "Accept: text/markdown" "$url" This release also standardizes generated command names to kebab-case. For example, cf accounts billing getCredits becomes cf accounts billing get-credits. For the full list of breaking command and flag changes, refer to the Cloudflare CLI release notes ↗︎. For more information, refer to Find Cloudflare documentation with a coding agent.

Source
10-15-2026
Atlassian

[Fixed] Update to Confluence Content Restrictions V1 API behavior for read and update operations

Rollout: progressive rollout by tenant IN PROGRESS What's changing We are updating the behavior of the Confluence Cloud REST API V1 content restrictions endpoints to ensure consistency between view and edit access. Previously, it was possible for a principal (user or group) to hold an update (Can edit) restriction without holding the corresponding read (Can view) restriction on content that had view restrictions applied.After this change:All principals will hold either only the read restriction (Can view) or both the read and update restrictions (Can edit).If a principal holds both read and update restrictions, any API request to remove only the read restriction will result in a rejection.To move content into an "edit restricted" state for these principals, you must request the removal of all read restrictions.What you need to do If your application manages content restrictions via the Confluence Cloud REST API V1, review your implementation to ensure:When granting update access, you also include the read restriction for that principal.Your logic for removing restrictions accounts for the fact that read access is now a prerequisite for update access.

Source
10-15-2026
Claude

2.1.301

Added Added CLAUDE_CODE_RETRY_WATCHDOG_MAX_USAGE_LIMIT_WAIT_MS so unattended retry mode (CLAUDE_CODE_RETRY_WATCHDOG) ends a request at a usage limit that resets too far away instead of waiting Added OpenTelemetry tracing guidance to the claude-api skill, including setting up trace destinations with the ant CLI Added the % motion to vim mode: jump to the matching bracket, alone or with d/c/y Added rows to a mod's Input: a text field of several lines in the terminal, where Enter submits and Shift+Enter or a backslash before Enter starts a new line Added classifier_verdict and permission_mode to OpenTelemetry tool_decision events, so auto mode classifier decisions can be told apart from permission rules Added classifier_category to OpenTelemetry tool_decision events, naming the built-in rule a classifier block matched, when OTEL_LOG_TOOL_DETAILS=1 [VSCode] Added LaTeX math rendering in Claude's responses, including $$ and multi-line \[ … \] blocks and inline $…$ and \(…\) math [VSCode] Added a "Get more usage" link to the usage-limit banner for Pro and Max plans in the VS Code and JetBrains panels Changed Changed a mod hook's .catch handler to run only when the hook throws or times out; events raised beneath the hook's own calls now skip that hook without asking its .catch Changed a mod's $.env.set to resolve with {} once the variable is set or unset, or with { deny } saying why when the write is not made Improved Improved switching to a model with a smaller context window: a conversation too long for the new model is now summarized by the previous model first Improved rendering performance while a long-running subagent works: its progress trail now updates incrementally instead of being reprocessed in full on every render Improved artifacts: pages Claude writes now paint the band above a sticky header, so scrolled text no longer shows there in the mobile apps Improved mods: in VS Code and the desktop and mobile apps, a tree drawn above the question dialog can now hold Markdown and up to 48 rows; the terminal keeps 12 plain rows

Source
10-15-2026
Atlassian

[Added] (Experimental) New REST APIs for managing and applying space policies in Jira Cloud

What's changing We've introduced new experimental REST APIs for managing space policies in Jira Cloud. Space policies allow site administrators to govern the creation and usage of fields and statuses in team-managed spaces, helping to prevent configuration sprawl and maintain instance health.The following experimental endpoints are now available:Viewing policiesGET /rest/api/3/policies — Get all policiesGET /rest/api/3/policies/project/{projectIdOrKey} — Get project policy stateGET /rest/api/3/policies/project/{projectIdOrKey}/rules — Get project policy rulesApplying policies to projectsPOST /rest/api/3/policies/{policyId}/apply — Apply a policy to projectsPOST /rest/api/3/policies/{policyId}/remove — Remove a policy from projectsPUT /rest/api/3/policies/project/{projectIdOrKey}/policies — Set the policies applied to a projectPOST /rest/api/3/policies/project/{projectIdOrKey}/validate — Validate policy application to a projectWhat you need to doReview the Jira Cloud space policy API documentation to understand the available methods and data structures.Note that these APIs are currently experimental and may change without notice.If you are building integrations that create fields or statuses, ensure you handle potential blocks when a space policy is active.

Source
On demo you can only see one page. Register for full history and email notifications.