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

Historical changes

1849 entries from demo-selected APIs

08-07-2026
Atlassian

[Announcement] Connect End of Support (EOS) date extended to January 31, 2027

What is changing?We are extending the Connect End of Support (EOS) date from December 2026 to January 31, 2027. This extension is intended to give partners and developers additional runway to complete their migrations without overlapping with end-of-year activities and annual planning cycles.For more information, please read  https://www.atlassian.com/blog/development/getting-ready-for-connect-end-of-support 

Source
08-07-2026
Claude

2.1.224

Added self-hosted environments: claude self-hosted-runner turns your own machines or containers into a place Claude Code web, mobile, and desktop sessions can run, on Team and Enterprise plans Added archive plugin source: install plugins from a zip over HTTPS without git or npm, with optional SHA-256 pinning Added a cancel-and-confirm step when removing an unavailable paste changes a command's text Added ANTHROPIC_BEDROCK_REGION_PREFIX env var for Bedrock to prefer a specific cross-region inference profile over the AWS_REGION-derived one Added crossSessionInbound and dialogExpiry settings: cross-session messages sent to a session running with bypassed permissions are held for your approval, and messages to other sessions auto-deliver Added sandbox credential-masking options: extract and onExtractNoMatch for structured env values, decode: "jwt" with maskClaims for JWT-aware masking, and awsPairs/sigv4 for AWS SigV4 re-signing; these need network.tlsTerminate and are honored only from user, managed, or --settings settings Added cross-session SendMessage: Claude Code sessions can now message each other, on any of your machines, with ListAgents to discover them (macOS and Linux) Fixed long (>200 char) project paths resolving to another project's session directory under a shared sanitized prefix; session list, rename, fork, delete and /resume no longer cross projects Fixed SendMessage reporting "Message sent" when the write to a teammate's inbox had actually failed; failed deliveries are now reported as errors Fixed sandbox filesystem deny entries written with a trailing slash (e.g. denyRead: "~/.aws/") being silently bypassable on Linux and macOS Fixed sandbox violation details never appearing in Bash tool results; Claude now sees which file or network access was denied and why Fixed MCP tools that connect mid-turn being deferred for tool search without their names announced to the model Fixed plugin install records being silently corrupted when the same plugin is installed in multiple projects Fixed recalled or restored paste content occasionally attaching wrong data or silently losing text when the paste had aged out or placeholder numbers collided Fixed copy-on-select on Wayland sometimes not reaching the clipboard; the two selection writes no longer race Fixed the feedback survey's transcript share silently failing on long sessions; a failed share now shows an error instead of a success message Fixed Remote Control auto-start intermittently failing with "Remote credentials fetch failed" on a cold start with a stale login token Fixed Remote Control and SDK clients showing a blank "(no content)" message after /clear and other output-less commands Fixed a Remote Control session recreated after its server session expired uploading prior local conversation history into the new session Improved fullscreen mode to keep the full pre-compaction history in scrollback across repeated compactions, instead of only the most recent interval Improved Remote Control: attached web and mobile clients now see compaction progress and the post-compaction boundary instead of a silent pause; /clear resets now propagate to attached clients Improved Remote Control: connection failures now show a persistent failure indicator with details and a reconnect shortcut, instead of only an 8-second toast Removed the 200-subagent-per-session spawn cap; long-running sessions no longer refuse new agents (concurrency and depth limits still apply) Changed managed settings: the approval prompt no longer re-appears after re-login or org switching when the organization's settings are unchanged Changed the feedback-survey transcript share: with your consent it now also uploads the last request's model settings — the system prompt (which includes your CLAUDE.md instructions), tool definitions, and model parameters. Secrets are redacted as before, and these fields are dropped first if the share is too large Changed the Bash tool description to always note that command output is displayed to the model, not reliably to the user Changed recalled paste placeholder numbers to renumber when accepted into the input Changed Remote Control to archive the stale server session instead of leaving a dead one listed when a fresh session is minted after compaction or /resume [VSCode] Fixed the extension showing Remote Control as connected after the connection failed Fixed a session resume silently reconnecting Remote Control after the user turned it off (--resume, SDK hosts, and the VS Code extension) [VSCode] Fixed sessions not honoring remoteControlAtStartup when explicitly enabled

Source
08-07-2026
Cloudflare

AI Gateway, Workers AI - Workers AI and AI Gateway unify model access and billing

Workers AI and AI Gateway now provide a unified path for accessing models and managing inference traffic. Use the same AI binding and REST API to call models hosted on Workers AI or by supported third-party providers, with AI Gateway providing observability, logging, caching, security, and billing controls. Unified entrypoints and observability The AI binding supports both Workers AI and third-party models through env.AI.run(). The REST API provides shared /ai/ endpoints with Cloudflare authentication across providers. Route a Workers AI request through AI Gateway by specifying a gateway ID. Use default to automatically create a gateway on the first authenticated request, or specify an existing gateway to separate applications and workloads: const response = await env.AI.run( "@cf/zai-org/glm-5.2", { messages: [{ role: "user", content: "What is the capital of France?" }], }, { gateway: { id: "default" }, }, );const response = await env.AI.run( "@cf/zai-org/glm-5.2", { messages: [{ role: "user", content: "What is the capital of France?" }], }, { gateway: { id: "default" }, }, ); Requests routed through AI Gateway can be logged and included in analytics for request volume, errors, latency, token usage, and costs. You can also configure controls such as caching, rate limiting, and request retries on the gateway. Unified billing and higher rate limits You can now use prepaid AI Gateway credits to pay for Workers AI inference. This provides one credit balance for Workers AI and supported third-party model providers. To use credits for Workers AI, set the gateway's Workers AI billing setting to Unified billing. Workers AI requests routed through that gateway deduct from your credit balance in real time. Prepaid credits also provide access to the following Workers AI frontier models without requiring the Workers Paid plan. Each frontier Workers AI model has a rate limit of 50 requests per minute per account, per model when billed with AI Gateway credits, compared to 20 requests per minute through standard Workers AI billing: @cf/moonshotai/kimi-k2.6 @cf/moonshotai/kimi-k2.7-code @cf/zai-org/glm-5.2 These limits are designed for typical agentic and coding workloads, where requests to frontier models can take longer to complete. For details, refer to Workers AI limits, Workers AI pricing, Unified Billing, and the AI Gateway model catalog.

Source
08-06-2026
Atlassian

[Deprecation Notice] Deprecation of confluence:fullPage and jira:fullPage modules

We are deprecating the confluence:fullPage(Preview) and jira:fullPage(Preview) modules on 30 Sep 2026. These modules are being replaced by the new global:fullPage(Preview) module, which provides a unified way to create immersive, full-screen experiences for your Forge apps across Atlassian products.The global:fullPage module is based on the same underlying infrastructure as the product-specific modules, so you can expect a consistent experience with minimal migration effort.What you need to do To ensure your apps continue to function correctly, you must migrate to the global:fullPage module before the deprecation date.Update your app manifest to use the global:fullPage module.Define the compatibility property in your manifest to specify which Atlassian products your app requires.Update any internal routing or links to use the new URL format: https://<site-hostname>/apps/full-page/<installation-id>/<route-prefix>/<app-route>.For detailed migration steps and configuration options, refer to the global:fullPage documentation.

Source
08-06-2026
Atlassian

[Added] Forge Teamwork Graph API can now be called from app frontends

What's changing The Teamwork Graph API can now be called directly from Forge app frontends (UI Kit and Custom UI) as part of the Teamwork Graph EAP. This is enabled via the new Forge bridge API, requestTeamworkGraph().Previously, Teamwork Graph queries could only be executed from the Forge backend using @forge/api. This update allows you to fetch unified context across Atlassian products directly from the client side, reducing latency and simplifying app architecture.What you need to doUpdate the @forge/bridge package to the latest version in your app's frontend directory:npm install @forge/bridge@latestEnsure your app has the required permissions in manifest.yml:For Jira: read:graph:jira For Confluence: read:graph:confluenceFor more details on implementation and available data, see the requestTeamworkGraph documentation and the Teamwork Graph API guide.To participate in this release, you must be enrolled in the Teamwork Graph EAP.

Source
08-06-2026
Claude

2.1.223

Added owner wildcard entries ("owner/*") to the strictKnownMarketplaces and blockedMarketplaces managed settings for allowing or blocking all marketplace repos under a GitHub org Added a warning when workflow agents, forked skills, slash commands, or resumed background agents' requested subagent model is restricted and the parent model runs instead Added a /teleport hint in cloud sessions showing how to continue locally with claude --teleport Fixed a Bash permission bypass where a crafted command could hide parts of itself from permission checks Fixed permission prompts so commands padded with tabs or invisible Unicode can no longer hide part of the command from the approval dialog Fixed workflow scripts being able to use dynamic import() to run code outside the workflow sandbox Fixed a permission gap where an agent definition's bypassPermissions mode ignored the org bypass-permissions disable policy Fixed resuming a session after a mid-session /cd coming back empty Fixed gateway model discovery hiding Claude models registered under provider-prefixed IDs such as vertex_ai/claude-* or bedrock/anthropic.claude-* Fixed modelOverrides keys that aren't Anthropic model IDs being treated as the session's canonical model ID; unknown keys are now ignored as documented Fixed managed settings: server-delivered settings no longer disable the env block of a machine-local managed-settings.json or MDM profile; admin env now merges per key Fixed sandboxed commands failing to start on Linux when sandbox.filesystem.denyWrite covers the working directory Fixed forked background agents getting stuck "already resuming" for the rest of the session when rebuilding the fork's parent prompt failed during resume Fixed a resumed session failing every turn, or leaving the interactive app on an unresponsive error screen, when its history held a malformed diagnostics attachment Fixed a rare hang when parsing unusual git push output Changed CLAUDE_CODE_DISABLE_1M_CONTEXT to hold every Claude model with a native 1M window to 200K via auto-compaction, not just a fixed list; a startup warning now appears when auto-compaction isn't holding the session to 200K Changed auto-compact to keep sessions on unrecognized model IDs within the assumed context window instead of letting them grow past it; set CLAUDE_CODE_DISABLE_UNKNOWN_MODEL_WINDOW_ENFORCEMENT=1 to restore the previous behavior Changed /review to be an alias of /code-review, which reviews the current diff or a PR (/code-review ); use /code-review ultra for a deep cloud review Changed /code-review with no effort level to reuse the level you typed last; type a level like /code-review high to change it

Source
08-06-2026
Cloudflare

AI Search - AI Search makes it easier to build a search engine for your data

AI Search gets you from a data source to a working search endpoint quickly. This release adds what you need to put that endpoint in front of real users: your own domain, authentication, and one endpoint across several instances. It also adds crawling for sites without a complete sitemap, so your index covers everything you want it to find. Each of the following is a new option. The previous behavior is still the default, so nothing changes until you change it. Serve search from your own domain A public endpoint is a URL that a site or app can query directly, with no authentication in front of it. By default that URL is a generated hostname on search.ai.cloudflare.com. You can now serve the same endpoint from a custom domain, a hostname in a zone that you own: https://search.example.com/search Restrict who can query your content Once your endpoint is on your own domain, you can put Cloudflare Access in front of it. For example, you usually want to give /mcp to specific agents rather than to anyone who finds the URL. Agents authenticate with an Access service token, and people who open the endpoint in a browser sign in through your identity provider. Search several instances from one URL A namespace can expose its own public endpoint with /search, /chat/completions, and /mcp paths that fan out across the instances you choose: curl https://ns-.search.ai.cloudflare.com/search \ --header "Content-Type: application/json" \ --data '{ "messages": [{ "content": "How do I configure AI Search?", "role": "user" }], "ai_search_options": { "instance_ids": ["docs", "support"] } }' Index your sites without a sitemap Website data sources support a new discover parse type. It starts at the source URL and collects pages from both your sitemaps and the links it finds while crawling: curl -X POST "https://api.cloudflare.com/client/v4/accounts//ai-search/instances" \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "id": "my-ai-search", "type": "web-crawler", "source": "example.com", "source_params": { "web_crawler": { "parse_type": "discover", "discover_options": { "source": "links", "limit": 5000, "depth": 3 } } } }' To learn more, refer to the AI Search documentation.

Source
08-06-2026
Cloudflare

Browser Run - Introducing Kitesurf, an agent-first browser on Browser Run

Kitesurf is Cloudflare's new stateless, highly scalable browser that runs entirely on top of Workers and is designed for AI agents. It is available for free while in beta. Compared to Chromium, Kitesurf uses 3–7× less CPU and memory for common agentic tasks like screenshots and HTML extraction, so you can run more sessions and scale better for bursty, AI-driven workloads. Your existing clients already work. To opt in, add the browser=kitesurf parameter to any Browser Run CDP or Quick Action endpoint: curl -X POST 'https://api.cloudflare.com/client/v4/accounts//browser-run/screenshot?browser=kitesurf' \ -H 'Authorization: Bearer ' \ -H 'Content-Type: application/json' \ -d '{ "url": "https://example.com" }' \ --output "screenshot.png" You can also explore Kitesurf without writing any code in the public playground ↗. For more information, refer to the Kitesurf documentation and the blog announcement ↗.

Source
08-05-2026
Amazon SP-API

New: Introducing the Tracking API v2026-01-30

The Tracking API v2026-01-30 is now available in the US store. You can use this API to retrieve tracking details for a shipment as it moves through Amazon’s supply chain. For more information, refer to the Release notes .

Source
08-05-2026
Amazon SP-API

SP-API Updates: Delivery Shipment Invoice API changes and LISTINGS_ITEM_ISSUES_CHANGE v 1.0 deprecation

This week's SP-API updates include changes to the getInvoiceStatus operation (Brazil store) to support multiple invoices per shipment, and the deprecation of LISTINGS_ITEM_ISSUES_CHANGE notification v1.0. Update to Delivery Shipment Invoice API getInvoiceStatus operations LISTINGS_ITEM_ISSUES_CHANGE...

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