For the following API endpoint:
https://api.hubapi.com/cms/blogs/2026-03/authors
sort doesn’t work for updatedAt, additionally example in docs suggests it’s a POST request rather than a GET request, however in the reference it’s marked as a GET request.
I tried the following (GET requests) query params:
?sort=-updatedAt
?sort=updatedAt
?sort=-updated
?sort=updated
The POST request equivalent wants a body, I saw some examples on the forum so I tried passing it, but then I get into a different set of errors.
“created” works perfectly, perhaps there is an internal name that is being used?
Any ideas on how to solve this? updatedAt is the most relevant for my usecase thanks.
Hey @msdev,
Thanks for posting in the Community!
I’m not seeing any pattern of error internally that would identify the cause of this behavior.
I’d like to tag in a few experts here to see what insight they might have. @stefen, @zach_threadint, and @BarryGrennan - any idea why @msdev is seeing these errors?
Shane, Senior Community Moderator
I’ve been able to replicate the issue flagged here by @msdev. The sort query parameter does not seem to be working as expected, at least according to this documentation. Could you please take a deeper look into this, @STierney? 
For example, the following 2 requests produced the exact same response, when actually we’d expect the 2 Author records to be ordered differently based on the supplied sort query parameter’s direction (i.e. ?sort=updatedAt and ?sort=-updatedAt -- where the difference between the 2 is the ‘-’ supplied immediately before updatedAt).
Request 1
curl --location 'https://api.hubapi.com/cms/blogs/2026-03/authors?sort=-updatedAt' \
--header 'Authorization: Bearer pat-xxx-redacted-xxx'
Request 2
curl --location 'https://api.hubapi.com/cms/blogs/2026-03/authors?sort=updatedAt' \
--header 'Authorization: Bearer pat-xxx-redacted-xxx'
Identical response body for both above requests
{
"total": 2,
"results": [
{
"avatar": "https://app.hubspot.com/settings/avatar/d41d8cd98f00b204e9800998ecf8427e",
"bio": "",
"created": "2024-01-18T01:55:38.315Z",
"deletedAt": "1970-01-01T00:00:00Z",
"displayName": "Test Author",
"email": "",
"facebook": "",
"fullName": "Test Author",
"id": "90785153008",
"language": "en",
"linkedin": "",
"name": "Test Author",
"slug": "test-author",
"twitter": "",
"updated": "2024-01-18T01:55:38.315Z",
"website": ""
},
{
"avatar": "",
"bio": "test author 2 bio",
"created": "2026-05-20T03:52:49.745Z",
"deletedAt": "1970-01-01T00:00:00Z",
"displayName": "Test Author 2",
"email": "test-author-2@example.com",
"facebook": "",
"fullName": "Test Author 2",
"id": "407901951173",
"language": "en",
"linkedin": "",
"name": "Test Author 2",
"slug": "test-author-2",
"twitter": "",
"updated": "2026-05-20T03:52:49.745Z",
"website": ""
}
]
}
Furthermore, the documentation’s “Sorting and paginating” example seems to be incorrectly using the “POST” request method. Shouldn’t that be “GET” and then remove the “Content-Type” header?
I hope this proves helpful. Please let me know if you have any follow-up questions.
Hey Zach (and the rest of the team) thanks for getting back to me.
Do you have an estimate as to how long before a fix is pushed?
Thanks!
Hey @msdev,
I’ve flagged this with the team internally, and I will be sure to keep you posted as soon as I hear something!
@zach_threadint - thank you so much for following up here! I’ll be sure to tag you into my follow-up!
Shane, Senior Community Moderator
Hey @msdev and @zach_threadint,
The team has confirmed that this was an internal error that has since been fixed! Would you mind confirming?
Shane, Senior Community Moderator
Hi @STierney 
Thanks for the update. I’m not seeing any difference yet. I’ll try again in the coming days.
Hi @STierney
I’ve just tested again and am still seeing the same behaviour I described in my first post on this topic. Please let me know if you have any follow-up questions.
Hey @zach_threadint thanks so much for getting back to us and for your patience.
Let me check on this and I’ll update you as soon as possible.
Thanks,
Bérangère
Hey @zach_threadint, thanks for your patience!
This is now fixed so you should be good to go!
Let me know if you have any questions, I am here for you!
Have a wonderful day!
Bérangère
Hi @Berangere
I’m still seeing the same behaviour I described in my first post on this topic. Please let me know if you have any follow-up questions.
Hey @zach_threadint,
Stepping back in, as @Berangere is out for the weekend.
Our internal team has provided the following context (quoting in an effort to not mis-communicate any of this):
"Has the customer tried using updated yet? I checked the code, the actual field map key is updated. updatedAt won’t work.
When the sort parameter is provided, it gets converted to snake case before being used, updatedAt will becomes updated_at, but still doesn’t match the actual key updated.
I tested this in my portal, and sorting by updated works as expected.
Could you ask the customer to try using updated as the sort parameter?
Note: For “create”, the key should also be created, so the way the customer is currently sorting by created is correct."
Would you mind confirming this on your end for us?
Shane, Senior Community Moderator
Hi @STierney
Thanks for the update. I can confirm that updated/ -updated and created / -createdwork as expected as values of the sort query string parameter. Just need the documentation updated to reflect this, as it still references updatedAt / -updatedAt and createdAt / -createdAt. Thanks very much 
Hey @zach_threadint,
Thanks so much for confirming this! I’ve passed your request to get the documentation updated along to the team.
Thanks so much for flagging this, and thank you for your ongoing patience!
Shane, Senior Community Moderator