Hello from the API.
" } }' ``` Copy the numeric ID from the fetch response into `spaceId`, not the space key you see in the URL. The body must be storage-format XHTML, so plain text without tags won't render as you expect. When the create succeeds, it returns the new page's `id`, its `title`, the `spaceId`, and a `version` object. Take the `id` and fetch the page again to confirm the body stored as written. ## Confluence API rate limits, quotas and pricing When it's overloaded, Confluence Cloud answers with `HTTP 429 Too Many Requests`, throttles by **cost-based points rather than a flat request count**, and Atlassian publishes no per-call price for API access. ### Confluence API rate limiting rules Count on two layers of points budgets, as Atlassian's docs describe them. One's a global pool per app. The other's a per-tenant pool that varies by edition. A cheap read and an expensive query don't cost the same, so a request count tells you little about how close you are. The pool you exhaust depends on who else is calling, not only on your own loop. | | Quota | Who shares it | Retry-After | Per-call price | |---|---|---|---|---| | Tier 1 Global Pool | Hourly points budget per app | Every tenant using your app | Honor it when the 429 carries it | Not published | | Tier 2 Per-Tenant Pool | Varies by edition | Everything calling that one site | Honor it when the 429 carries it | Not published | | 429 handling | Triggered when a pool is spent | Whoever exhausted the pool | Header tells you how long to wait | Not published | Because the per-tenant pool's shared, one noisy integration on a customer's site can starve yours. Your code did nothing wrong, and it still gets the 429. There's nothing to meter or forecast per request, because Atlassian doesn't publish a per-call price. **API access comes with the Confluence plan**. When a 429 arrives, treat the `Retry-After` header as the authority when it's present. Without it, back off exponentially and add jitter so parallel workers don't retry in lockstep. Cap your retries, and log the endpoint that tripped the limit. Expensive calls are what spend points fastest, so that log shows where to cut. ## Fix common Confluence API errors When a call fails, nearly every cause traces to credentials, a permission that hides content, a malformed or stale write, or throttling, and each answers to a status code you can read. Match the code, check the cause, and only then touch your retry logic. | Status | Usual cause | Fix | Docs | |---|---|---|---| | 400 | Invalid storage-format body or wrong field | Validate the markup, set the representation to `storage` | [v2 intro](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) | | 401 | Wrong email/token pair or malformed auth header | Regenerate the token, send email plus token as Basic auth | [v2 intro](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) | | 403 | Account lacks the space or page permission | Grant access to the account that owns the token | [v2 intro](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) | | 404 | Wrong ID, or permissions hiding a page that exists | Check the ID, then check the token's account can view it | [v2 intro](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) | | 409 | Stale version number on update | Fetch the current version, resend with it incremented | [v2 intro](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) | | 429 | Rate limit hit | Honor `Retry-After`, back off, reduce request cost | [Rate limiting](https://developer.atlassian.com/cloud/confluence/rate-limiting/) | | Pagination cursors | Results cut off, or cursor rebuilt by hand | Follow the `next` link in `_links` | [v2 intro](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) | If you get a 401, Confluence doesn't know who you are, so look at the email and token pairing. A 403 means it knows you and said no, so look at the account's permissions, not your code. When a page you can see in the browser returns a 404, the token's account usually can't view it. A 400 on write usually means the storage-format body isn't valid markup. **Someone edited between your read and your write**, so updates must carry the next version number: re-read, reapply, resend. ## Call the same Confluence endpoints with Activepieces ### Using a visual workflow instead of a cursor loop Activepieces lets you build the same Confluence calls as a flow, with the credential held centrally as a connection instead of pasted into each script. Its Confluence piece covers common actions, and its HTTP step can call any v2 or v1 endpoint the piece doesn't wrap, so the gaps you fall back to v1 for are still reachable. ### What the workflow looks like In the screenshot below, a three-step flow starts with a Typeform trigger labeled "New Submission", passes through an AI Agent step labeled "Influencer Management", and ends on an Asana action labeled "Create Task".  Swap the last step for a Confluence page-creation call and you have the shape of the job. Read the right panel closely, though: the Typeform trigger shows "Throws an error, reconnect or refresh the page" beside the required Connection and Form fields. That's the failure you'll meet first, and it's a credential problem, not a logic problem. Fix the connection, then use "Test Trigger" or "Generate Sample Data" before you trust anything downstream.  ### Where this approach fits That's the clean case: one trigger, one request, a body you can read at a glance, a form submission that becomes a Confluence page. Put the token in a connection, not in the step body, so it's stored once and not pasted into every flow. Low volume, one space, and a stable page template are what this suits.  ### When to call the Confluence API in code Don't expect the visual builder to remove Confluence's cost-based rate limiting or its permission errors; it only hides where they surface. A flow that returns a 403 because the token's user can't see the space fails exactly as your script would, with less room to inspect it. Move to code when you need custom retry and backoff. Move to code too when you page through large result sets and must follow `next` links with state, or when volume's high enough that you need to control request cost yourself. For teams who need to work with Confluence through a workflow tool, Activepieces is the better choice on the criterion of reach: its Confluence piece covers the common actions, and its HTTP step can call any v2 or v1 endpoint the piece doesn't wrap, so a missing built-in action is a starting point rather than a dead end.  The credential is held centrally as a connection instead of pasted into each script, and because the catalogue is open source and can be checked directly in the monorepo, a reader can verify what is covered rather than trust a marketing figure. A team that prefers to write and maintain its own cursor-loop code may still value that control, but for anyone who wants the same Confluence calls without those gaps becoming ceilings, the visual flow is the stronger option. ## Frequently asked questions You pay for the seats, not the requests. Atlassian doesn't list a separate charge for the Confluence Cloud REST API, and calls run as a user on your existing plan and count against the same [rate limits and permissions](https://developer.atlassian.com/cloud/confluence/rest/v2/intro/) as everything else. On a free plan, Atlassian's REST API docs don't gate Cloud API access behind a paid tier. On a Free site you can authenticate with an API token and call the endpoints. Treat the plan's own limits on users and features as the ceiling, and check them in [Atlassian's API token guide](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) before you build on it. If you're on Data Center, this API doesn't work, at least not the one this article covers. The v2 API and the token flow described here are Cloud-only. Data Center ships its own REST API with its own authentication, documented in [Atlassian's Data Center REST reference](https://developer.atlassian.com/server/confluence/confluence-server-rest-api/). A script written against a Cloud URL will fail against a Data Center host. ### Why does my API token stop working? Usually one of four causes: the token expired, someone revoked it, the account behind it was deactivated, or that user lost access to the space you're calling. Tokens carry an expiry set at creation, and they act as the user who made them, so they can never see more than that user can. Manage and re-issue them in [Atlassian's token docs](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/). A sudden `401` points at the token, while a `403` points at permissions. Through v1, attachment uploads work. The v2 attachment endpoints cover reading and deleting, so uploads are one of the gaps where you fall back, using the [v1 attachments endpoints](https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content---attachments/). Send a multipart request with the `X-Atlassian-Token: no-check` header, or Confluence rejects it as a possible cross-site request. ## Related reading - [Confluence Pricing: Free and Paid Plans (2026 Guide)](https://www.activepieces.com/blog/confluence-pricing-free-and-paid-plans-2026-guide) - [Best AI Agent Builders for Sales Teams, Ranked](https://www.activepieces.com/blog/best-ai-agent-builders-for-sales-teams-ranked) - [Best AI Agent Builders in 2026: Ranked & Reviewed](https://www.activepieces.com/blog/best-ai-agent-builders) ## References - [Atlassian](https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-comment/)