# Using filters with OData/API calls
You can provide filters in API calls to get targeted information in return. The syntax for this follows the Microsoft REST API guidelines<https://github.com/Microsoft/api-guidelines/blob/master/Guidelines.md#97-filtering>. For example, to GET all open (unpaid) sales invoices above 1000.00 excl tax, call `<endpoint>/companies(bb6d48b6-c7b2-4a38-9a93-ad5506407f12)/salesInvoices?$filter=status eq 'Open' and totalAmountExcludingTax gt 1000.00`
You can either filter by range or by property. To learn how to develop a good filter expression, see devenv-entering-criteria-in-filters. To know more about filter expressions and their equivalent AL expressions in web services, check out ../webservices/use-filter-expressions-in-odata-uris#filter-expressions.
> NOTE
> There's a special filter, journals.templateDisplayName, which returns journals if a user hasn't defined the filter criteria.
## Related information
Developing connect apps for Dynamics 365 Business Central<devenv-develop-connect-apps>
Working with webhooks in Dynamics 365 Business Central<../api-reference/v2.0/dynamics-subscriptions>
Tips for working with the APIs<devenv-connect-apps-tips>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-connect-apps-filtering, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-connect-apps-filtering/
