private async Task<GridData<Model>> ServerReload(GridState<Model> state)
{
	// via the GridState, the MudDataGrid will provide information on pagination, searching and filtering.
	// The FilterDefinition class allows for retrieving the filter as Expression or as Func<T, bool>.
	// For transfer to an API the easiest approach is to project the definitions to their respective expression
	// And use the ToString() overloaded method of the Expression type to be able to serialize the resolved expression:
	var filterStrings = state.FilterDefinitions.Select(fd => fd.GenerateFilterExpression().ToString());

	// using this List<string> of filters, you can forward this information to the API (usually you will have some sort of RequestDto carrying more information like pagination and sorting)
	var requestDto = CreateRequestDto(..., filterStrings); // some custom logic to create your request model.

	var response = await SomeService.GetModels(requestDto); // fetch data from the API

	// ... Some error handling most likey happening here...

	return new GridData<Model>() { TotalItems = response.TotalRecords, Items = response.Data };
}

// ...
// From the API, you can take the filter information from your request DTO and use them in your data query.
// When using for example EntityFramework.Core to fetch your data from a DB, the most convenient approach would
// be to use System.Linq.Dynamic.Core package and simply feed the filters to your IQueryable instance:
public async Task<PagedResponse<Model>> GetModels(YourRequestDto filter)
{
	var baseQuery = AppDbContext.Models.AsNoTracking();
	var combinedFilter = String.Join(" or ", filter.FilterStrings) // of course you can also use " and " to combine individual filters
	var filteredQuery = baseQuery.Where(combinedFilter); // This line requires System.Linq.Dynamic.Core to work

	// perform further steps on your db entities (e.g. sorting, pagination, projection etc.)
	// ...
	return serviceResponse;
}