The Reporting API provides programmatic methods to access Mural report data. These reports reveal granular information about your company’s activities.
Key benefits include:
- Get consistent and reliable access to key reports on a self-serve basis.
- Conduct regular reviews of configuration settings.
- Manage member attributes and access to Mural.
- Understand the engagement and usage of Mural to manage software operational costs.
The Reporting API has two types of reports: core reports and membership reports.
These reports provide information about an organization's account levels, and the association of users at each level, using aggregate metrics.
Each core report is associated with a Mural account level: workspace, room, mural, user, template.
Here’s a list of core reports:
These reports provide information about users and their membership details for the account levels they are associated with. Membership is defined as the association of a user to their account level.
User types can include Members, Administrators, and Guests. Association types (between users and levels) include admin, owner, member, or guest.
Here’s a list of membership reports:
- Workspace Memberships
- Room Memberships
- Mural Memberships
Need a refresher on Mural's accounts and organizational structure? See this Help Center article: How are Mural accounts organized?
Members are collaborators that are part of your company domain. They can own and access any content that an admin or mural owner permits them to.
Guests are people outside of your company that are invited to collaborate on a project with you. Guests have limited use of Mural. They cannot invite others, create or manage rooms, create, duplicate, or export murals, publish templates, or push murals to a touchscreen device.
Admins are collaborators in your company domain who have the authority to administer access to Mural. A company can have company admins and workspace admins.
Reporting API data is not real time. Reports are made available within 24–48 hours. If you make a request and the time range overlaps with the last 24–48 hours, you may not see all events during this time frame.
Filter and sort options for GET endpoints are not currently available.
To ensure a high quality user experience and to prevent abuse and security issues, the Reporting API enforces a rate limit of 1,500 calls per day per customer (roughly 1 call per minute).
To narrow the results of each report, you can filter them to better suit your needs. You do this using a filter query parameter. By setting this parameter, you are giving the report something to compare each row of the report against. Every row that matches your parameter is then included in your final report, and every row that doesn’t match is left out.
This section walks you through creating filter query parameters, but you can also use the API reference page for each report to generate these query parameters for you.
The filter query parameter relies on the following syntax:
Here’s what each of those elements represents:
- column: The column of data you want to run through your filter criteria. For example,
- operator: An optional operator to help bridge the gap between your column’s data and your expression. For example,
lessThan. Valid operators depend on the data type of the column.
- expression: The criteria you want your data to meet to be included in your report. For example, a specific date. Valid expressions depend on the data type of the column.
Here are some common examples of filters you can use with reports. You’ll find more details about how to filter each report on its dedicated page, but these give a general overview.
To generate a report of workspaces that have been deleted after a certain date, use the filter parameter:
And to generate a report of workspaces that have been deleted prior to a certain date, use the filter parameter:
You could combine these two filters for an even more customized report. Here’s what that combined filter parameter looks like:
If no date filter is used, the report returns data from all time by default.
In cases where your filter criteria is an either or value, you use a boolean value of true or false. To generate a report of murals that have been deleted, use the filter parameter:
And to generate a report of murals that have not been deleted, use the filter parameter:
Sometimes, you might be filtering using a column that has a set list of possible values. For example, the report column shareLinkMemberPermission can have three possible values:
readOnly. Here, choose the value that suits your needs and use that in your parameter.
Here’s what that filter parameter looks like:
When dealing with columns that hold numerical data, include an operator that works as an indication of comparison. For example, if you want a report of murals with more than 100 members,
100 is your expression and
greaterThan is your operator.
Here’s what that filter parameter looks like:
The following operators are supported:
You can filter columns of numeric data without using an operator, however there will be an implied operator of
equals. For example, the two following expressions have the same filtering result:
Company admins on the Mural Enterprise plan.
Company admins create API keys using the Mural company dashboard. With an API key, they make HTTP requests to the Reporting API and receive JSON response data.
Eager to jump right in? Here's a quick summary to get up and running immediately.
- Log in to Mural.
- Go to the company dashboard.
- On the left side of the company dashboard, click API Keys.
- Click Create API Key.
- Select the Reports checkbox.
- Click the Create API key button.
- Copy the API key and share it with your team.
That's it! You're now ready to start making API calls.
Updated about 1 month ago