Loading ...

REST API: Create Forum Post | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Forums » REST API: Forum Posts (Discussion Replies) » REST API: Create Forum Post
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 27

REST API: Create Forum Post

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

Provides programmatic access for the creation and processing of get multiple 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 post JSONStringYESBodyThis is JSON that represents a post 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.
EntityTypeIntegerYESBodyEntity Type of the forum post is 54
ContentTitleStringYESBodyTitle of the forum post
ContentBodyStringYESBodyDescription of the forum post
ParentContentIDIntegerYESBodyID of the topic under which the post is to be created
GrandParentContentIDIntegerYESBodyThe forum Content ID
SpaceIDIntegerYESBodyUnique ID of the space. Space ID should be 0 for Top Level Community.

Optional Parameters

ParameterTypeRequiredLocationDescription
AuthorIDIntegerNOBodyAuthor's unique ID. It can be used for ghostwriting purposes.
ReplyToPostIDIntegerNOBodyThe ID of the post under which you are going to leave a post
IsFeaturedBooleanNOBodyUsed to mark post as "featured"

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

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

Request Body

{
  "ContentTitle": "RE: Battery discharge issue",
  "ParentContentID": 1,
  "GrandParentContentID": 236,
  "EntityType": 54,
  "ContentBody": "You have been doing a nice job!",
  "SpaceID": 0
}

Success Response

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

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