topic Re: Fetch List Memberships API sorting order changed recently, now it does not match the document... in APIs & Integrations

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

sean-laxis — Fri, 14 Feb 2025 09:30:13 GMT

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 }

Re: Fetch List Memberships API sorting order changed recently, now it does not match the document...

Jaycee_Lewis — Fri, 14 Feb 2025 23:18:04 GMT

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

Re: Fetch List Memberships API sorting order changed recently, now it does not match the document...

sean-laxis — Mon, 17 Feb 2025 00:37:26 GMT

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

Re: Fetch List Memberships API sorting order changed recently, now it does not match the documentati

daniloaf — Thu, 10 Apr 2025 21:20:11 GMT

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