Loading ...

REST API: Get Activity Stream of a User | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Wall Posts » REST API: Get Activity Stream of a User
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 37

REST API: Get Activity Stream of a User

0 
 /5
0 (0votes)
Open API Guide
GET/api/wall/stream

Enables administrators and developers to programmatically retrieve a mixed feed of social activity. This combines wall posts, article updates, and other community news into one "Activity Wall". It's the "Pulse" of your community and the perfect content for a home page feed.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.

Required Parameters

ParameterTypeRequiredLocationDescription
UserIDIntegerYESQueryID of the user whose wall posts and activities are to be returned

Optional Parameters

ParameterTypeRequiredLocationDescription
StartPageIntegerNOQuerySpecifies the starting page of list to be returned
PageLengthIntegerNOQuerySpecifies the number of results to be returned per page

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/api/wall/stream?userid=1&startpage=1&pagelength=100

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": [
    {
      "EntityComments": [],
      "EntityCommentCount": 0,
      "CustomEntityActivityComments": [],
      "DisplayOption": 0,
      "WallID": 0,
      "WallContentType": 0,
      "OEmbedProviderType": 0,
      "FromUserID": 1,
      "ToUserID": 0,
      "SpaceID": 252,
      "DateCreated": "2026-01-01T12:00:00Z",
      "WallComment": [],
      "ActivityFeedID": 6788,
      "ActivityEntityType": 10,
      "ActivityEntityTypeID": 10,
      "ActivityContentTypeID": 0,
      "ActivityEntityID": 242,
      "ActivityAction": 1,
      "IsFeed": false,
      "CanBeCommented": false,
      "CanBeLiked": false,
      "CanBeDeleted": false,
      "ParentEntityID": 0
    },
    {
      "EntityComments": [],
      "EntityCommentCount": 0,
      "CustomEntityActivityComments": [],
      "DisplayOption": 0,
      "PermissionCheckEntityID": 0,
      "WallID": 0,
      "WallContentType": 0,
      "OEmbedProviderType": 0,
      "FromUserID": 1,
      "ToUserID": 0,
      "SpaceID": 252,
      "DateCreated": "2026-01-01T12:00:00Z",
      "WallComment": [],
      "ActivityFeedID": 6787,
      "ActivityEntityType": 10,
      "ActivityEntityTypeID": 10,
      "ActivityContentTypeID": 0,
      "ActivityEntityID": 241,
      "ActivityAction": 1,
      "IsFeed": false,
      "CanBeCommented": false,
      "CanBeLiked": false,
      "CanBeDeleted": false,
      "ParentEntityID": 0
    },
    {
      "EntityComments": [],
      "EntityCommentCount": 0,
      "CustomEntityActivityComments": [],
      "DisplayOption": 0,
      "PermissionCheckEntityID": 0,
      "WallID": 0,
      "WallContentType": 0,
      "OEmbedProviderType": 0,
      "FromUserID": 1,
      "ToUserID": 0,
      "SpaceID": 252,
      "DateCreated": "2026-01-01T12:00:00Z",
      "WallComment": [],
      "ActivityFeedID": 6786,
      "ActivityEntityType": 10,
      "ActivityEntityTypeID": 10,
      "ActivityContentTypeID": 0,
      "ActivityEntityID": 240,
      "ActivityAction": 1,
      "IsFeed": false,
      "CanBeCommented": false,
      "CanBeLiked": false,
      "CanBeDeleted": false,
      "ParentEntityID": 0
    }
  ]
}

Error Response

{
  "IsError": true,
  "ResponseMessage": "Required parameter is missing or invalid.",
  "ResponseData": null
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestOne or more required fields are missing or invalid.Verify the request payload against the required parameters.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
404 Not FoundThe specified user was not found.Verify the userID is correct.
500 Server ErrorInternal failure.Retry later.

Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

  • Sustained Request Rate: Do not exceed 5 API calls per second
  • Sequential Processing: Wait for each request to complete before sending the next in automated workflows
  • Concurrent Connections: If parallel processing is required, limit to 3 or fewer simultaneous requests
  • Response Timeout: Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.

Wiki Index

Pages