Here are my current issues:
1. Why does Atlassian request a site URL if it is only going to state that it doesn't exist? I cut n pasted as well as manually typed the confluence address for my company and the response was it doesn't exist.
2. When I use the Confluence APIs to retrieve page views, the recurring issue is that Confluence can't transform the stream to valid JSON. I have tried the documentation example as well. Here is the error:
HTTP status: 500
{
"data": {
"authorized": true,
"errors": [],
"successful": true,
"valid": true
},
"message": "com.atlassian.confluence.api.service.exceptions.ecosystem.ServiceException: Unable to transform stream to valid JSON ",
"statusCode": 500
}
And here is a very basic code sample trying to test it for a single page ID. Authentication details aren't listed in the sample but assume that yes the API token is correct etc. (works fine for other types of calls).
The fact that you're getting a 500 with "Unable to transform stream to valid JSON" while the response body simultaneously says "successful": true is a server-side serialization bug — it's not your code. You're not the only one hitting this. Another community member reported that around April 2025.
The API docs list it as an optional parameter. Unbounded requests against pages with large view histories seem to trigger the serialization failure more often. Can you try something like ?fromDate=2026-06-01 to limit the data range?
Hello @erikka_innes
Welcome to the Atlassian community.
Are you referring to the URL field in the Atlassian Support Portal where support cases can be opened? If so Atlassian restricts creation of support cases to people who are administrators of the Organization or the Application. If you aren't an admin at that level then you will get that message because it is not "finding" the specified URL under the list of sites which you administer.
If you contact your administrators they can open the support case for you and share it with you so that you can interact with support directly.
Can you print out the response as plain text rather than trying to process it as JSON?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.