Fetch List Memberships API sorting order changed recently, now it does not match the documentation
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
}
Fetch List Memberships API sorting order changed recently, now it does not match the documentation
Hey, @sean-laxis 👋 Thanks for flagging. I get the same result in my tests. I'll update here with any information I receive. — Jaycee
|
Join us on March 27th at 12 PM for the Digital Essentials Lab, an interactive session designed to redefine your digital strategy! Engage with expert Jourdan Guyton to gain actionable insights, participate in live Q&A, and learn strategies to boost your business success. Don't miss this opportunity to connect and grow—reserve your spot today! |
 | Did you know that the Community is available in other languages? Join regional conversations by changing your language settings ! |
