Open topic with navigation

# Filters for Durables

You can filter client durables by attribute and value. Methods first filter the durables, and then apply any action to the durables that meet the filtering criteria. Filtering applies to all persistence status methods at the durable level.

If a `GET` method returns a collection of durable status objects as its top level value, then you can filter the collection based on JSON attributes of the durable objects in the collection.

For example, `GET persistence/<clus_name>/stores/<stor_name>/durables` returns a collection of durable objects. You can filter the collection to durables that match one or more top level attribute values. For example, the filter `?type=standard&dynamic=true` gets only dynamic standard durables.

Similarly, if a `POST` method affects a collection of durable status objects, then you can target a narrower collection by adding filter parameters to the request. The action of the method applies after filtering the collection. You can use this technique to selectively purge a narrower collection of durables from a persistence store.

## JSON Attributes for Filtering Durables

You can filter by any top-level JSON attribute of durables that has a scalar, string, or boolean value. Nonetheless, the following are the most useful attributes for filtering durables:

- `type=<type>`
- `name=<dur_name>`
- `client_id=<ID>`
- `dynamic=<bool>`
- `filter=<filter_string>`
- `staticOnly=true`
- `dynamicOnly=true`

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.