1589 entries from demo-selected APIs
The stream-stall hint now reads "Waiting for API response · will retry in …" instead of "No response from API · Retrying in …", and triggers after 20s of silence instead of 10s
DescriptionQuotes reporting is now available via Marketplace reporting APIs. We're introducing Quotes reporting to the Atlassian Marketplace reporting APIs. Partners can now programmatically retrieve their accepted quotes and export quotes data in bulk.What's changingYou can now access accepted-quote data for your apps through the reporting APIs:List accepted quotes — a paginated list of accepted quotes for your apps, with filtering by product, creation date, acceptance date, and entitlement period.Quote details — line-level detail for a single quote (including schedules and discounts), looked up by quoteId and/or quoteNumber.Async export — initiate a bulk export of accepted quotes, poll its status, and download the resulting CSV/JSON file (recommended for large datasets).API changesThe following endpoints are available for Quotes reporting.Vendor (v2):GET rest/2/vendors/{vendorId}/reporting/quotes(link)GET rest/2/vendors/{vendorId}/reporting/quotes/details(link)POST rest/2/vendors/{vendorId}/reporting/quotes/async/export(link)GET rest/2/vendors/{vendorId}/reporting/quotes/async/export/{exportId}/status(link)GET rest/2/vendors/{vendorId}/reporting/quotes/async/export/{exportId}(link)Developer-space (v3):GET rest/3/reporting/developer-space/{developerId}/quotes(link)GET rest/3/reporting/developer-space/{developerId}/quotes/details(link)POST rest/3/reporting/developer-space/{developerId}/quotes/async/export(link)GET rest/3/reporting/developer-space/{developerId}/quotes/async/export/{exportId}/status(link)GET rest/3/reporting/developer-space/{developerId}/quotes/async/export/{exportId}(link)Key query parameters (list endpoint): productId, startDate, endDate, acceptedStartDate, acceptedEndDate, entitlementStartDate, entitlementEndDate, limit, offset.Quote details: provide quoteId and/or quoteNumber (optionally entitlementNumber).Async export: filter by createdStartDate/createdEndDate, acceptedStartDate/acceptedEndDate, entitlementStartDate/entitlementEndDate, and choose accept=csv or accept=json. At least one complete date range pair is required.Sample API responseGET rest/3/reporting/developer-space/{developerId}/quotes?startDate=2025-01-01&endDate=2025-01-31{ "_links": { "self": { "href": "/rest/3/reporting/developer-space/{developerId}/quotes?startDate=2025-01-01&endDate=2025-01-31" }, "query": { "href": "/rest/3/reporting/developer-space/{developerId}/quotes{?productId*,startDate,endDate,acceptedStartDate,acceptedEndDate,entitlementStartDate,entitlementEndDate,limit,offset}", "templated": true }, "next": { "href": "/rest/3/reporting/developer-space/{developerId}/quotes?startDate=2025-01-01&endDate=2025-01-31&offset=10&limit=10" } }, "quotes": [ { "quoteId": "Q-12345", "quoteNumber": "QT-000123", "quoteStatus": "ACCEPTED", "quoteCreatedDate": "2025-01-05", "acceptedDate": "2025-01-10", "quoteExpiryDate": "2025-02-05", "entitlementNumber": "E-111-AAA-AAA-11A", "productId": "acd011b1-1111-45bc-902a-247046a11111", "productName": "Test App", "appEdition": "Advanced", "technicalContactCompany": "Test Company", "technicalEmail": "test@example.com", "startDate": "2025-02-01", "endDate": "2026-02-01", "userTier": 100, "listPrice": 1200.00, "discounts": [ { "promotionId": "PROMO-1", "amount": 120.00, "percent": 10.0, "reasonCode": "LOYALTY", "type": "EXPERT", "promoCode": "SAVE10" } ], "createdBy": "partner@example.com", "vendorId": "1213041", "productPlatform": "cloud", "commerceSystem": "CART" } ] }Action requiredNo action is required to keep existing integrations working.If you want to consume quotes data:Use the vendor endpoints (/rest/2/vendors/{vendorId}/...) for vendor-scoped access, or the developer-space endpoints (/rest/3/reporting/developer-space/{developerId}/...) for developer-scoped access across all your apps.For large result sets, prefer the async export flow (initiate → poll status → download) rather than the synchronous list endpoint.
What’s changingWe’ve released a preview of new modal sizing capabilities, giving you more control over how your app's modals appear and behave.Custom pixel sizes: You can now pass specific width and height values in pixels to define the exact dimensions of your modal.Runtime resizing: You can enable dynamic resizing by adding viewportSize: resizable to modal extension points in your manifest, or by passing resizable to the size prop in UI Kit and @forge/bridge modal.What you need to do As this feature is currently in preview, we encourage you to test these new configurations in your development environments:For extension points: Update your manifest.yml to include the viewportSize: resizable attribute or viewportSize: { width, height } for relevant modules.For UI Kit or Bridge: Update your modal calls to use supported css string values for width and height, or set the size prop to resizable.For detailed implementation details, refer to the updated documentation: https://developer.atlassian.com/platform/forge/apis-reference/ui-api-bridge/modal/#modal https://developer.atlassian.com/platform/forge/ui-kit/components/modal/ https://developer.atlassian.com/platform/forge/manifest-reference/modules/
What's changingNew skill: forge-cost-optimizer – Analyzes your Forge app's resource usage and recommends optimizations to reduce invocation costs.New skill: forge-security-review – Performs automated security checks against common vulnerabilities and Atlassian best practices before deployment.New skill: forge-connector – Helps scaffold and configure connections between Forge apps and external services.Updated: forge-app-review – Now provides a lightweight release-readiness review covering permissions, manifest hygiene, and common deployment blockers.Codex support – Added Codex as an installation option for the plugin and individual skills.What you need to doIf you're using the Forge AI Plugin, update to the latest version to access the new cost optimizer and security review features.To install via Codex, follow the new Codex installation steps in the relevant skill or plugin docs.
Improved auto mode safety: destructive git commands (git reset --hard, git checkout -- ., git clean -fd, git stash drop) are now blocked when you didn't ask to discard local work, git commit --amend is blocked when the commit wasn't made by the agent this session, and terraform destroy/pulumi destroy/cdk destroy are blocked unless you asked for the specific stack Added a warning when the requested model is deprecated or automatically updated to a newer model, shown on stderr in print mode (-p) and now also covering models set in agent frontmatter Added attribution.sessionUrl setting to omit the claude.ai session link from commits and PRs in web and Remote Control sessions Added /config --help to list all available shorthand keys for /config key=value Changed /config toggle behavior: Enter and Space both change the selected setting, and Esc now saves and closes instead of reverting Removed the startup "setup issues" line under the logo — run /doctor to see configuration issues or use --debug Fixed thinking.disabled.display: Extra inputs are not permitted 400 errors on subagent spawns and session-title generation for affected configurations Fixed WebSearch returning empty results in subagents Fixed the terminal cursor being stranded above the prompt after navigating history in vim mode with the native cursor enabled Fixed fullscreen TUI corruption (statusline mid-screen, duplicated spinner rows, merged text) in Windows Terminal under heavy nested-subagent load Fixed turns silently completing with no visible output when the model returned only a thinking block; Claude now re-prompts once Fixed user-level skills appearing multiple times in slash-command autocomplete when multiple plugins are enabled Fixed MCP servers requiring authentication exposing auth-stub tools to the model in headless/SDK mode Fixed tmux teammate panes failing to launch when the shell has slow rc-file initialization, and keystrokes typed during agent spawn leaking into the new tmux pane instead of the leader prompt Fixed background tasks started by a teammate being killed when the teammate finishes a turn Fixed scheduled task and webhook trigger deliveries being treated as keyboard input; they now classify as task notifications and can no longer approve a pending action or set the session title in auto mode Fixed focus mode showing "Ran N PostToolUse hooks" timing lines under each response
As part of end of support for Connect app, we will be deprecating application property APIs.When we reach Connect EOL, the following endpoints will be removed:GET /repositories/{workspace}/{repo_slug}/commit/{commit}/properties/{app_key}/{property_name}PUT /repositories/{workspace}/{repo_slug}/commit/{commit}/properties/{app_key}/{property_name}DEL /repositories/{workspace}/{repo_slug}/commit/{commit}/properties/{app_key}/{property_name}GET /repositories/{workspace}/{repo_slug}/properties/{app_key}/{property_name}PUT /repositories/{workspace}/{repo_slug}/properties/{app_key}/{property_name}DEL /repositories/{workspace}/{repo_slug}/properties/{app_key}/{property_name}GET /repositories/{workspace}/{repo_slug}/pullrequests/{pullrequest_id}/properties/{app_key}/{property_name}PUT /repositories/{workspace}/{repo_slug}/pullrequests/{pullrequest_id}/properties/{app_key}/{property_name}DEL /repositories/{workspace}/{repo_slug}/pullrequests/{pullrequest_id}/properties/{app_key}/{property_name}GET /users/{selected_user}/properties/{app_key}/{property_name}PUT /users/{selected_user}/properties/{app_key}/{property_name}DEL /users/{selected_user}/properties/{app_key}/{property_name}
The Routes page in the Cloudflare dashboard now shows the routes across all of your connectors — Cloudflare Mesh and Cloudflare Tunnel routes alongside Cloudflare WAN and Magic Transit static routes — in a single table, instead of a separate routes view per product. From the unified Routes page you can: Visualize your network with an interactive map that shows how your destinations flow through to your connectors — including equal-cost multi-path (ECMP) routes where the same prefix is served by several connectors. Select a node to filter the table down to the routes behind it. See every route in one table, with its destination, type, connector, priority, and source, and filter or sort to find what you need. Create, edit, and delete routes of any supported type without leaving the page. When adding a Cloudflare WAN or Magic Transit static route, you now pick the next hop by connector name instead of typing its IP. Manage virtual networks from a dedicated tab. Test a route to see which connector and next hop a destination resolves to before you commit a change. To find it, go to Networking > Routes in the dashboard sidebar. Go to Routes Your existing routes, APIs, and configurations are unchanged — this is a dashboard experience that brings them together in one place. Learn how to add routes and manage virtual networks.
Durable Objects now remain alive for the duration of active outbound connections created via connect() or an outbound WebSocket. Previously, a Durable Object would be evicted after 70-140 seconds of no incoming traffic, even if the object had an open outbound connection, which is a common pattern when streaming responses from a large language model (LLM) over TCP or an outbound WebSocket. With this change, each active outbound connection prevents eviction. Once all outbound connections close, the standard 70-140 second inactivity window applies before the Durable Object is evicted. Before: streaming connections were cut off by eviction After: active outbound connections keep the Durable Object alive If you are building agents on Cloudflare, this is especially relevant. An agent that streams tokens from an LLM while calling models, or that performs long-running tasks over an outbound connection, now stays alive for the duration of that connection instead of being evicted mid-stream. Limits: Each outbound connection keeps the Durable Object alive for a maximum of 15 minutes. After 15 minutes, the connection stops preventing eviction (the connection itself continues operating), and the standard eviction rules resume. The Durable Object's existing per-account instance limits still apply. For more information, refer to Lifecycle of a Durable Object.
Durable Objects now supports two new location hints for Asia-Pacific: apac-ne (Northeast Asia-Pacific) and apac-se (Southeast Asia-Pacific). Use apac-ne or apac-se when you want finer-grained placement within Asia-Pacific rather than the broader apac hint. Use the new hints the same way as any other locationHint: // Northeast Asia-Pacific (Japan, Korea, etc.)const stubNE = env.MY_DURABLE_OBJECT.get(id, { locationHint: "apac-ne" }); // Southeast Asia-Pacific (Singapore, Indonesia, etc.)const stubSE = env.MY_DURABLE_OBJECT.get(id, { locationHint: "apac-se" }); If your users are spread across all of Asia-Pacific, the existing apac hint remains the right choice. Only reach for apac-ne or apac-se when your traffic is clearly concentrated in one sub-region and you want to minimize round-trip time to that audience. The default behavior and what we generally recommended is not adding a location hint unless absolutely needed, this will create the Durable Object as close to the initializing request as possible to reduce latency. As with all location hints, these are best-effort suggestions. Cloudflare will place the Durable Object in a nearby data center, not necessarily the exact hinted location. For the full list of supported hints, refer to Data location — Provide a location hint.
AI agents can now deploy Workers to Cloudflare without first requiring a user to sign up, open a browser-based OAuth flow, click through the dashboard, or create an API token. When an agent tries to deploy without Cloudflare credentials, Wrangler can tell it to rerun with --temporary, then deploy the Worker to a temporary preview account. To try this with your agent, update to Wrangler 4.102.0 or later, make sure you are logged out (wrangler logout), and then ask your agent to build something and deploy it to Cloudflare. The agent should follow Wrangler's output and deploy using the --temporary flag. wrangler deploy --temporary The temporary deployment stays live for 60 minutes. During that window, the agent can verify the Worker, redeploy changes, and return both the live Worker URL and claim URL. Opening the claim URL lets you sign in to or create a Cloudflare account and make the temporary account permanent. Temporary preview accounts currently support a limited set of products, including Workers, Workers Static Assets, Workers KV, D1, Durable Objects, Hyperdrive, Queues, and SSL/TLS certificates. For supported products, limits, and claim behavior, refer to Claim deployments (temporary accounts). For more context, refer to Temporary Cloudflare Accounts for Agents.
Tell us which API you want to monitor and we can prioritize adding it to the platform.
FedEx shipping, tracking, and developer platform changelog updates
GitHub platform and changelog updates
GitLab release and platform updates
Google Maps JavaScript API release notes and platform updates.
HubSpot developer platform and changelog updates
AI search and answer platform for developers.
Storefront and admin API updates
Slack platform and developer changelog updates
Stripe API and developer changelog updates
TikTok Shop developer documentation and platform updates
Twilio developer platform and API changelog updates
UPS shipping, tracking, and developer portal changelog updates
This is for Walmart US Marketplace API
General Walmart Marketplace release notes, operational changes, business updates, and platform announcements
WooCommerce developer release posts and platform updates
Zoom developer platform and changelog updates
The live demo supports up to 5 APIs at a time in this browser session.