Erskine Wilson

Hi Erica,

Thanks for responding, but this doesn't solve my problem. It's easy to make a button. 

The issue is that API calls to follow and unfollow sections made by an end user require authentication. Please advise.

Hi there,

I'm trying to create my own version of the "subscribe" button for a section in an attempt to make a version of this button that will also subscribe the end user to all of the section's subsections. I was under the impression that I could take advantage of the CSRF token described here to make the POST/DELETE requests needed to "follow" or "unfollow."

So far, however, my attempts have been unsuccessful, and it isn't clear to me if this token can actually be used for this purpose. 

Strangely, I did discover that the "list section subscription" endpoint works even without any token or authentication header for an end user, which I don't really understand. 

I'd be grateful for any information or suggestions.

I'd also like to see this implemented for the same purpose (release notes/archival material that is worth keeping but shouldn't appear in article search results). 

My current solution to this is a custom page for release notes that's essentially a copy of an article page in terms of layout. This is very impractical though since I need to bury old release notes inside accordions to keep the page clean, and even then the html is not going to be great to work with after a while. If you only care about having the latest release notes published though, it works okay.