What is the default order or records in a get request when no view or sort order is applied

[Cameron_Flanaga]

How are records ordered in a GET request when no view or sortby parameters are entered. I dont understand the order of the default response.

[ScottWorld]

Bill.French:

Nor should you care. Here’s why… integrations should exist without the influence of users who may apply various sort order changes which would create a degree of brittleness at the integration layer.

This is 100% true… although it would be nice to know what sort of internal algorithm Airtable is using for the default sorting of its records via the API. Is this where the sandwich bet comes in? :smiling_face_with_sunglasses: :sandwich:

[Bill_French]

ScottWorld:

it would be nice to know what sort of internal algorithm Airtable is using for the default sorting of its records via the API

That’s just it, there is no [apparent] sorting; it’s simply how they read the data from the storage layer. The algorithm likely has nothing to do with Airtable; more likely it has to do with the underlying database platform it all sits on and the recall performance requirements. They won’t reveal it because even they probably don’t know nor do they care to know.

My take - APIs (unless explicitly told otherwise) tend to hand you the data as fast as possible and that often means you get a tossed record salad.

ScottWorld:

Is this where the sandwich bet comes in?

You and I are on the “random” behavior. If there are others who believe it is not random, they need to bet against our horse. So far, I don’t see any takers. @Kamille_Parks?

[ScottWorld]

Bill.French:

That’s just it, there is no [apparent] sorting; it’s simply how they read the data from the storage layer. The algorithm likely has nothing to do with Airtable; more likely it has to do with the underlying database platform it all sits on and the recall performance requirements. They won’t reveal it because even they probably don’t know nor do they care to know.

Ah, yes, I see what you’re saying. That makes perfect sense.

Bill.French:

APIs (unless explicitly told otherwise) tend to hand you the data as fast as possible and that often means you get a tossed record salad.

Yes, this also makes 100% perfect sense, and this is exactly how it should be for the fastest speeds!

Bill.French:

You and I are on the “random” behavior. If there are others who believe it is not random, they need to bet against our horse. So far, I don’t see any takers. @Kamille_Parks?

I’m hungry, people! Step up to the plate here!! :stuck_out_tongue_winking_eye:

[kuovonne]

ScottWorld:

Is this where the sandwich bet comes in?

My bet is that the current default sort order used on Nov 3, 2021 will not be documented on the support website within my lifetime. Even if a default sort order is ever documented, it will not be clear if the default sort is retroactive back to this date. Unfortunately, it will be impossible for me to win this bet.

[Kamille_Parks]

Oh no, count me out. I don’t even use the REST API lol

[Bill_French]

C’mon! You don’t have to use it to guess what it does. Triple or nothing bet?

[Nicolas_d_ANDRE]

@ScottWorld How would you guys force the sorting criteria when not using API. In my case, I am using an Airtable search formula in Zapier (something simple like AND({Description}="Hardware",{Amount}>="1000")) and I need the search results to be sorted via a specific column on my view...

How would one do that ?

[ScottWorld]

@Nicolas_d_ANDRE 

I don’t use nor recommend Zapier anymore, because of TONS of limitations like this.

Make lets you search and sort records, and it’s all built natively into the product without needing to craft any custom API calls.

Make is significantly less expensive than Zapier, yet it is infinitely more powerful & customizable than Zapier.

There can be a bit of a learning curve with Make, which is why I created this basic navigation video for Make, along with providing the link to Make’s free training courses. There are also many Make experts hanging out there who can answer other Make questions. 

[Nicolas_d_ANDRE]

Thanks @ScottWorld - not the first time I am hearing that comment. I guess I'll give it a try. Start working on one workflow and if that's OK, start migrating...

[ScottWorld]

@Nicolas_d_ANDRE You won't regret it!