I’ve built a small n8n automation that pulls my daily Micro.blog activity through the JSON API — my replies plus the mentions directed at me — and appends a summary to my notes each evening. The replies side works perfectly; every mentions endpoint I try returns a 500.
Here’s what I’m seeing, all with the same app token, within the same run:
GET /posts/replies → 200, returns my replies as expected
GET /posts/mentions → 500
GET /posts/mentions/mb → 500
GET /posts/mentions/mastodon → 500
GET /posts/mentions/bluesky → 200, but empty (items: )
A few things that might help narrow it down:
The 500s return the generic HTML error page (“Error while processing the request…”), not a JSON auth error — and the same token pulls /posts/replies cleanly moments before and after, so it doesn’t look like a credential problem.
The aggregate /posts/mentions fails the same way with and without the count parameter.
It’s been consistent across July 17 and 18, several times a day, and status.micro.blog showed everything green throughout.
Is this a known issue, or something specific to my account (numericcitizen)? Happy to share exact timestamps or run any test that would help.
Title: Follow-up — the /posts/mentions 500 was triggered by the count parameter
Quick follow-up to my earlier post, in case it helps someone else.
I found the trigger: passing a count parameter to /posts/mentions is what caused the 500. Drop count from the query and the endpoint returns my mentions normally — confirmed from my n8n automation, using the same app token that had been getting the 500.
So, side by side:
GET /posts/mentions?count=100 → 500 (the generic HTML error page)
GET /posts/mentions → 200, returns mentions as expected
The per-source variants (/posts/mentions/mb, /posts/mentions/mastodon) also returned 500 while count was present. I’ve since consolidated back to the plain aggregate /posts/mentions with no count — it returns everything in one call and has been reliable since.
The reason I’d still flag it: the JSON API docs list count as a valid paging parameter, so /posts/mentions arguably should either honor it or ignore it gracefully rather than 500. Might be worth a look. Either way, my daily replies-and-mentions summary is working again — thanks to anyone who read the first post.