Loading ...

REST API: Create Forum Group | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Forums » REST API: Forum Groups » REST API: Create Forum Group
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 32

REST API: Create Forum Group

0 
 /5
0 (0votes)
Open API Guide
POST/api/content

Provides programmatic access for the creation and processing of add content resources.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.
Content-TypeYESapplication/jsonMust be set to application/json

Required Parameters

ParameterTypeRequiredLocationDescription
Forum Group JSONStringYESBodyThis is JSON that represents a forum group object that you're creating. This should be of the format seen below in the sample given. The required values in this JSON are given below.
EntityTypeStringYESBodyEntity Type for forum group is 2
ContentTitleStringYESBodyTitle of the forum group
MetaTitleStringYESBodyTitle of the group that will be displayed in search engine's result page
MetaDescriptionStringYESBodyDescription of the group that will be displayed in search engine's result page
MetaKeywordsStringYESBodyMeta Keywords are a specific type of meta tag that help tell search engines what the topic of the page is

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/content

Request Body

{
  "EntityType": "6",
  "ContentTitle": "General Discussion",
  "MetaTitle": "General Discussion Forum Group",
  "MetaDescription": "A forum group for general company discussions and announcements.",
  "MetaKeywords": "forum, discussion, general"
}

Success Response

{
  "IsError": false,
  "ResponseMessage": "ToBePublished",
  "ResponseData": 272
}

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. (content)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