Community API broken?

[Luka Hummel - codefortynine]

Hi guys,

I'm retrieving community posts via the API as documented here, and until 16 hours ago this worked without a hitch. Now the API just returns 404 errors.

Also note that the example links in the community post by @Tyler T are also broken.

Can you observe the same? Has there been some change?

[Sarp Egemen]

Hi @Luka Hummel - codefortynine ,

Yesterday, the community's address was changed from community.atlassian.com to community.atlassian.com/forums.

This is probably the reason your API calls are returning a "not found" status. Unfortunately, I am not aware of the new API endpoints. Currently, "https://community.atlassian.com/forums/api/" does not seem to be working.

[Luka Hummel - codefortynine]

That is a suspicious timing. Seems like the URL change messed up their API endpoints. 

[Matthias Gaiser _K15t_]

Good catch @Luka Hummel - codefortynine. I'll make sure to raise this with the community managers.

[Ansari_ Amir]

Hi @Luka Hummel - codefortynine 

Atlassian recently announced that they are setting the new and existing API keys to expire after 1 year.

This could be the reason that your API is returning 404 error.

Here's the link to the document

[Luka Hummel - codefortynine]

The community API actually didn't need any authentication in the past. Maybe that changed.

[Darryl Lee]

API access to Jira and Confluence are completely different from the API endpoints we were using in Community.

Atlassian Community is run on the Khoros platform, what has a fairly robust API for searching posts:

https://khoros.com/developer/community/community-rest-api-capabilities

Annoyingly their docs require (free) registration, but you can see a Python interface for it here:

https://khoros.readthedocs.io/en/latest/community-api-calls.html

But yeah, the Khoros Community APIs have always allowed anonymous access.