--- title: "Profile Summary" slug: "profile-summary" updated: 2024-03-29T23:02:26Z published: 2024-03-29T23:02:26Z canonical: "onpremises.webtrends.help/profile-summary" --- > ## Documentation Index > Fetch the complete documentation index at: https://onpremises.webtrends.help/llms.txt > Use this file to discover all available pages before exploring further. # Profile Summary /profiles/{profile ID} returns summary data for a profile, including the last time the profile was analyzed, so client applications can determine when to refresh data. The interval between updates is at least 15 minutes. **Method:** GET **URI:** /profiles/{profile ID}/ **Note:** Add any optional parameters to the end of the URI. If you change the order of URI or required parameters, or place optional parameters before them, the call will not work. Version number The version number you will use is dependant upon the version of Analytics you have installed. Analytics versions 9.5 and below, use v2_0. Analytics versions 9.5.1 and above will use v2_1. **Example Request** https://myDomain.com/{version}/ReportService/profiles/K729vc8Qqj5/?period=2021&format=xml **Example Response** ``` - - 10314 1esZ1fhWjd6 1esZ1fhWjd6 ! WebTrends Internal Collaboration profilestats - period - 2021 1 - - - 00:16:59 00:06:32 14,199,295 April 27, 2009 Thu 15:00-15:59 March 15, 2009 2009-09-23 14:49:59 - 140953 18876 97.37 2.63 0 386 7.47 51 15.22 1240 398 842 13922 140953 140953 100 0 0 0 0 2454 123 927 25 154 ``` The Most Active Date, Number of Hits on Most Active Date, Most Active Day of the Week, Most Active Hour of the Day, and Least Active Date fields are not populated if the time period is not relevant (for example, data for Most Active Date will not appear if the time period is a single day). ## Parameters: ### End period Use the end_period parameter to specify the ending day of a date range. You must also supply the **start_period**. **end_period** = ending day of date range **Example: specifying January 1, 2020 to January 30, 2020** start_period=2020m01d01&end_period=2020m01d30 **Example: specifying the past 7 days (from yesterday)** start_period=current_day-7&end_period=current_day-1 **Note:** Several time period macros are available: CURRENT_DAY, CURRENT_MONTH and CURRENT_YEAR. Instead of a specific start and end date, you can identify relative time periods. ### Format format = return data format Example: specifying data formats | Data format | Parameter and value | | --- | --- | | JSON | format=json | | XML | format=xml | | XML2 ("XPath-friendly" XML for dynamic applications) | format=xml2 | | HTML | format=html (use this when importing data into Excel) | | CSV | format=csv (returned as a download) | | RSS | format=rss (use to specify an RSS 2.0 syndication feed) | | ATOM | format=atom (use to specify an ATOM 1.0 syndication feed) | For report data requests, all formats are supported. For "list" requests, only XML and JSON formats are supported. ### Period Use the period parameter to specify the time period of interest and a trend length for report data. You can specify a relative time span or a specific time span (see [here](/v1/docs/list-report-time-periods)). Supplying only **period** is the same as supplying **start_period** and **end_period** with the same value. period = time period * trend length Example: getting data for a relative time period (current_day, current_month, current_year) | Time span | Parameter and value | | --- | --- | | Yesterday | period=current_day-1 | | Two months ago | period=current_month-2 | | Trending backward from February 28 | period=2024m02d28*28 | | Rolling 7-days-to-date trend | period=current_day-1*7 | | Year trend with holidays and annual cyclical data | period=current_month-1*12 | Example: getting data for a specific time span (year, quarter, month, week, day, hour) | Time span | Parameter and value | | --- | --- | | 2024 | period=2024 | | First quarter of 2024 | period=2024q01 | | January 2024 | period=2024m01 | | January, February and March 2024 | period=2024m03*3 | | 23rd week of 2023 | period=2023w23 | | January 1, 2024 | period=2024m01d01 | | January 1, 2024 through January 6, 2024 | period=2024m01d06*6 | ### Start period Use the start_period parameter to specify the beginning day of a date range. You must also supply the **end_period**. **start_period** = first day of date range **Example: specifying January 1, 2020 to January 30, 2020** start_period=2020m01d01&end_period=2020m01d30 **Example: specifying the past 7 days (from yesterday)** start_period=current_day-7&end_period=current_day-1 **Note:** Several time period macros are available: CURRENT_DAY, CURRENT_MONTH and CURRENT_YEAR. Instead of a specific start and end date, you can identify relative time periods. ### Suppress error codes Set the suppress_error_codes parameter to true if you do not want to be notified of error conditions for a request (the default is false). suppress_error_codes = {true|false} Example: Suppress errors for a request suppress_error_codes=true