Returns one page of an organization's members, with what each member did during a date range.

This list does not add up to memberCount. memberCount counts members who joined on or before to. This list shows every current member, whenever they joined. So meta.totalCount and memberCount can differ.

Query parameters

To send several values, repeat the parameter with brackets: status[]=active&status[]=inactive. One value can go without brackets.

Date range rules:

• The range can be at most 24 months long.
• from cannot be earlier than January, five years ago.
• to cannot be later than the current month.

Other rules:

• Out-of-range values are rejected, not adjusted. A perPage above 100, a page below 1, or an unknown sort, order, status or userType returns 400.
• (page - 1) * perPage cannot exceed 1,000,000.
• Every role is accepted for every organization type. A role the organization cannot have returns no rows. For example, maker in a classroom.
• Members with no value in the sort column come first when order is asc, and last when it is desc. For example, with sort=lastActivityDate, members who never did anything come first or last.

Row attributes

Each row's id is the member's user hashid.

What the list covers

• Current members only. A member who has left is not listed, even for a date range before they left.
• active means creating something. Only padlets, posts, comments and reactions count. A member who only viewed padlets is inactive.
• lastActivityDate is not tied to the range. It can fall before or after it. It also counts time spent on a padlet, so an inactive member can still have a date. It is null only if the member has no activity in the organization at all.
• There is no owner role. Owners show as admin, so userType[]=admin returns admins and the owner together. You cannot filter for the owner alone.

Meta

A failed list returns 200, not a 5xx. Always check meta.status before reading data. An empty data with failed is an error, not an empty organization.

Errors

Example

curl "https://api.padlet.dev/v1/organizations/$ORG_ID/analytics/users?from=2026-01-01&to=2026-03-31&status[]=active&sort=posts&order=desc&perPage=2" \
  -H "X-API-KEY: $PADLET_API_KEY"

{
  "data": [
    {
      "id": "user_abcd1234efgh5678",
      "type": "organizationAnalyticsUser",
      "attributes": {
        "name": "Ada Lovelace",
        "username": "ada",
        "email": "[email protected]",
        "userType": "teacher",
        "active": true,
        "signupDate": "2025-09-14",
        "lastActivityDate": "2026-03-02",
        "padlets": 4,
        "posts": 37,
        "comments": 12,
        "reactions": 58
      }
    },
    {
      "id": "user_wxyz9876stuv5432",
      "type": "organizationAnalyticsUser",
      "attributes": {
        "name": "Alan Turing",
        "username": "alan",
        "email": "[email protected]",
        "userType": "student",
        "active": true,
        "signupDate": "2025-08-21",
        "lastActivityDate": "2026-03-01",
        "padlets": 2,
        "posts": 19,
        "comments": 5,
        "reactions": 23
      }
    }
  ],
  "meta": {
    "status": "ready",
    "dateRange": { "from": "2026-01-01", "to": "2026-03-31" },
    "page": 1,
    "perPage": 2,
    "totalCount": 348,
    "totalPages": 174
  }
}

Exporting every member

Request page=1, 2, and so on until you pass meta.totalPages. Keep from, to and every filter the same on each request. If you change a filter partway, the pages shift and you can miss or repeat members.