Summary
We’re seeing a strange issue where pages created via the createConfluencePageV2 API endpoint return a successful response (200 OK) but never actually appear in Confluence. They’re not indexed, not visible in the UI, and can’t be retrieved through search or the content APIs, even though the API call itself reports success.
Issue Description
Whenever we submit a request to createConfluencePageV2, Confluence replies with HTTP 200 OK and no errors. However, those pages never show up anywhere:
- They don’t appear in the Confluence UI under any space or page tree.
- They don’t show up when we run a CQL search (e.g., title = "AVAgent ADF Test – Direct ID Fetch").
- They don’t show up in calls to /rest/api/content?space=....
In short, it’s as if Confluence acknowledges the request but never actually saves or indexes the new page. We’ve tried multiple spaces (including a team space and a personal space), and the behavior is identical everywhere.
How to Reproduce
- API Request
nginx
CopyEdit
POST https://api.atlassian.com/wiki/rest/api/content
(this is the underlying endpoint used by createConfluencePageV2)
CopyEdit
b775381d-868b-4412-a705-28aaf155a953
- Space IDs Tested:
- Team space (ASA space): 8817394668
- Personal space: ~712020670468013f184c35b353e19c8acdee5f
- Sample Payload (editor representation):
json
CopyEdit
{
"title": "AVAgent ADF Test – Direct ID Fetch",
"status": "current",
"spaceId": "~712020670468013f184c35b353e19c8acdee5f",
"body": {
"value": "{\"type\": \"doc\", \"version\": 1, \"content\": [{\"type\": \"paragraph\", \"content\": [{\"type\": \"text\", \"text\": \"ADF Test created by AVAgent. Will fetch by contentId.\"}]}]}",
"representation": "editor"
}
}
- Expected response: 200 OK, and a new Confluence page should appear.
- Actual response: 200 OK, but no new page shows up in Confluence.
- Verify in Confluence
- Run CQL (Confluence Query Language):
ini
CopyEdit
title = "AVAgent ADF Test – Direct ID Fetch"
→ No results returned.
- Call the content API to list pages in that space:
bash
CopyEdit
GET /rest/api/content?space=~712020670468013f184c35b353e19c8acdee5f
→ The newly “created” page is not in the list.
- Check Confluence UI manually:
→ No sign of the page in any space, page tree, or recent updates.
Additional Notes
- We have tested both representation: "editor" (as shown above) and representation: "storage". The outcome is identical—Confluence replies 200 but never persists the page.
- We used two different spaces (one team space, one personal space) to rule out permission issues.
- The personal space used for testing is one where our user has admin-level access, so it’s not a permissions problem.
- This behavior is reproducible in multiple workspaces, so it doesn’t look like a one-off bug tied to a single space or site configuration.
What We’re Asking
Could you please help us figure out:
- Indexing Delay or Bug?
- Is there a known delay between creating a page via the API and having it show up in search or the UI? We’ve waited several minutes and still see nothing.
- Hidden Permissions/Constraints?
- Are there any hidden settings or restrictions that might prevent an API‐created page from being committed to the content tree?
- Silent API Failure?
- Is it possible that the API is returning 200 OK but not actually saving the content? If so, what steps can we take to troubleshoot why the new page isn’t being written to Confluence?
Any guidance or insight you can provide would be greatly appreciated. Thanks!
