--- title: "How to get a list of all available objects" slug: "how-to-list-all-available-objects" updated: 2026-07-06T12:30:38Z published: 2026-07-06T12:30:38Z canonical: "docs.mapp.com/how-to-list-all-available-objects" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # How to get a list of all available objects The following methods can be used to retrieve a list of available objects to help you build API queries without using the frontend Export. Before you can call these lists, you should start and authenticate your API session as normal. > [!NOTE] > If you would like to get your results in German, you can change (?language=en) to (?language=de). If this is left off the call, it will default to English. ## Objects ```json GET api.mapp.com/api/analytics/query-objects(?language=en) ``` ### Basic Properties Returned | Name | Definition | | --- | --- | | name | API name (must be used in your requests) | | title | The title as seen on the site | | context | the default scope of the object | ### Example Result ```json   {      "name": "product_parameter_number_675_sum",            "dataType": "NUMBER",      "title": "Discount costs",                            "elementType": "CUSTOM_PARAMETER",      "metricDisplayType": "NORMAL"      "context": "ACTION"                          }, ``` Find detailed information on [this page](/v1-api/apidocs/list-all-available-dimensions-and-metrics). ## Dynamic Time Filters ```json GET api.mapp.com/api/analytics/dynamic-timefilters(?language=en) ``` ### Basic Properties Returned | Name | Definition | | --- | --- | | name | API name (must be used in your requests) | | title | the title, as seen on site | | dynamicFilter | contains the complete dynamic filter configuration inside { } | ### Example Result ```json {    "title": "Today, 14 days ago",    "name": "before_14_days",        "dynamicFilter": {                  "name": "time_dynamic",      "connector": "AND",      "filterPredicate": "LIKE",      "value1": "before_14_days",      "value2": "",      "context": "NONE"    }  }, ``` Find detailed information on [this page](/v1-api/apidocs/list-all-available-dynamic-timefilters). ## Segments ```json GET api.mapp.com/api/analytics/segments ``` ### Basic Properties Returned | Name | Definition | | --- | --- | | id | Segment ID (must be used in your requests) | | title | The title as seen on site | | description | The description as visible in the user interface | ### Example Result ```json {    "id": 1108,    "title": "Predicted conversion probability - Medium",      "description": "Percentile based, this includes the top 11% - 30% of all users ranked by conversion probability"  }, ``` Find detailed information on [this page](/v1-api/apidocs/list-all-available-segments). ## Example Use Case You want to replace a static time range with a dynamic one. ### Static example: ```json "predefinedContainer": {            "filters": [                {                    "name": "time_range",                    "filterPredicate": "BETWEEN",                    "connector": "AND",                    "caseSensitive": false,                    "context": "NONE",                    "intern": false,                    "value1": "2021-11-12 00:00:00",                    "value2": "2021-12-10 00:00:00"                }            ],            "containers": []        } ``` To use a dynamic time range instead of a static one, replace ```json { "name": "time_range", "filterPredicate": "BETWEEN", "connector": "AND", "caseSensitive": false, "context": "NONE", "intern": false, "value1": "2021-11-12 00:00:00", "value2": "2021-12-10 00:00:00" } ``` with ```json { "name": "time_dynamic", "connector": "AND", "filterPredicate": "LIKE", "value1": "before_14_days", "value2": "", "context": "NONE" } ``` ### Dynamic example: ```json {    "title": "Today, 14 days ago",    "name": "before_14_days",    "dynamicFilter": {      "name": "time_dynamic",      "connector": "AND",      "filterPredicate": "LIKE",      "value1": "before_14_days",      "value2": "",      "context": "NONE"    } }, ``` ## Trouble Shooting The information you gather from this call can be used to build your own custom requests. In case of an error or if something doesn't look quite right, our first suggestion is to check the same configuration onsite. By rebuilding your analysis in the UI and then downloading the JSON file, you can see where your request could be improved.