Fetch List Memberships API sorting order changed recently, now it does not match the documentation

Developer Support APIs & Integrations
1

According to the documentation of `/crm/v3/lists/{listId}/memberships/join-order`, the recordIds are sorted in ascending order if an after offset or no offset is provided.

However, the response is now in descending order. Last week the result was in ascending order.

Could you confirm if the API documentation is consistent with the API behavior? Thank you!

{
 "results": [
 {
 "recordId": "94465402289",
 "membershipTimestamp": "2025-02-05T02:55:10.877Z"
 },
 {
 "recordId": "94477778617",
 "membershipTimestamp": "2025-02-05T02:55:10.710Z"
 }
 ],
 "total": 2
}

seanlaxis_0-1739524237819.png
seanlaxis_0-1739524237819.png1594×1328 188 KB

seanlaxis_0-1739524701182.png
seanlaxis_0-1739524701182.png1142×878 147 KB

2

Hey, @sean-laxis :waving_hand: Thanks for flagging. I get the same result in my tests. I’ll update here with any information I receive. — Jaycee

3

Hi @Jaycee_Lewis , thank you for confirming this, we look forward to your update.

4

hey, @sean-laxis , same here, I just found this issue today