Activity and personalization

This guide explains how to retrieve user activity and recently interacted content using AISquare APIs.

Overview

AISquare provides endpoints to:

• Retrieve user activity
• Fetch recently viewed resources

These endpoints return data specific to the authenticated user.

User activity

This endpoint returns a list of activities associated with the authenticated user.

Endpoint

GET /api/v1/activity/

Query parameters

Access control

• Requires authentication
• Returns 401 if user is not authenticated

Response

• Paginated list of user activities
• Each item represents an activity record

Retrieve a specific activity

Endpoint

GET /api/v1/activity/{id}/

Path parameters

Access control

• Requires authentication
• Returns 404 if activity is not found

Continue where you left off

This endpoint returns recently viewed resources for the user.

Endpoint

POST /api/v1/aistudios/continue-where-left-off/

Request body

1
{
2
  "url": "ai-research-studio"
3
}

Query parameters

Access control

• Requires authentication
• Returns 400 if url is missing or invalid
• Returns 404 if publication is not found

Response includes

Each item represents a recently viewed resource with:

• experience_id
• experience_uid
• experience_title
• experience_description
• resource_type
• resource_id
• resource_uid
• resource_title
• cover_image

Publication data

• publication_id
• publication_title
• publication_logo
• publication_custom_url

Metrics

• views
• likes
• shares
• bookmarks

Creator

• id
• username
• full_name
• profile_picture

Additional fields

• tags
• trending_score
• last_activity
• created_at
• updated_at

Notes

• Results are scoped to the authenticated user
• Returns recently viewed resources only
• Uses a flattened response structure

Error responses

When to use these endpoints

Related pages

• AI Studios — continue-where-left-off is an AI Studio endpoint
• Authentication — required for all activity endpoints
• Core Concepts — activity in the entity hierarchy
• User onboarding — personalization through per-user accounts
• Metrics and analytics — related engagement data
• Errors — handle 400, 401, 404 responses