Loading ...

REST API: Change Forum Topic Subscription | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Forums » REST API: Forum Topics (Discussions) » REST API: Change Forum Topic Subscription
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 37

REST API: Change Forum Topic Subscription

0 
 /5
0 (0votes)
Open API Guide
PUT/api/content/subscription

Changes a user's forum topic (discussion) subscription

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens
Content-TypeYESapplication/jsonMedia type of the request body

Required Parameters

ParameterTypeRequiredLocationDescription
EntityTypeIntegerYESQueryEntity type for topic is 55
ContentIDIntegerYESQueryUnique identifier for a particular topic
UserIDIntegerYESQueryID of the user whose subscription needs to be changed
IsSubscribeBooleanYESBodySpecifies if the topic is subscribed by the user. Accepted values: true false

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/content/subscription?EntityType=55&ContentID=5&UserID=64

Request Body

true

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": true
}

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. (entityType, contentID, userID)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.
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