Use lists to create and maintain sets of values that may be referenced in rule conditions. Commonly used lists contain values related to conditions that target specific properties such as: customers, transactions, or BINs.
You may grant list edit permissions to members of your team without enabling them to edit rules. This may be useful if your workflow involves frequent updates to value sets that are used in rule or bind conditions. List order may not be maintained and duplicates may be removed.
For more information, see Value lists.
Retrieves a collection of lists. This operation returns the most recent version of each list.
Criteria for filtering collection items. This field requires a special format. Use , to specify multiple allowed values. Use ; to specify multiple fields.
For more information, see Search filters.
- Mock serverhttps://www.rebilly.com/_mock/catalog/all/lists
- Sandbox serverhttps://api-sandbox.rebilly.com/organizations/{organizationId}/lists
- Live serverhttps://api.rebilly.com/organizations/{organizationId}/lists
curl -i -X GET \
'https://www.rebilly.com/_mock/catalog/all/lists?limit=0&offset=0&filter=string&sort=string&fields=string&q=string' \
-H 'REB-APIKEY: YOUR_API_KEY_HERE'Collection of lists retrieved.
Total number of items that match the request. The value is independent of limit, including when limit is 0.
Date and time when the resource is created. This value is set automatically when the resource is created.
Date and time when the resource is updated. This value is set automatically when the resource is updated.
[ { "id": "lst_0YVCXVQH84DEF93D8VBTJQ9TGK", "version": 1, "description": "string", "values": [ … ], "createdTime": "2019-08-24T14:15:22Z", "updatedTime": "2019-08-24T14:15:22Z", "_links": [ … ] } ]