Loading ...

REST API: Update Persona | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Users » REST API: Personas » REST API: Update Persona
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 23

REST API: Update Persona

0 
 /5
0 (0votes)
Open API Guide
PUT/api/personas/{PersonaID}

Used to update an existing persona.

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
NameStringYESBodyName of Persona created
PersonaIDIntegerYESPathID of Persona to update

Optional Parameters

ParameterTypeRequiredLocationDescription
IsEnabledBooleanNOBodyIf Persona created is to be active or not. True or False. Default is False
IncludeActionsBooleanNOBodyIndicates if actions are included when conditions are met. True or False
RunActionOnSaveBooleanNOBodyIndicates if actions made will run when persona is created. True or False
PersonaMatchConditionIntegerNOBody0 = Match all conditions 1 = Match any conditions
ProfileFieldIdIntegerNOBodyField to compare condition with. See How to get a ProfileFieldId documentation.
ConditionOperatorTypeIntegerNOBodyEquals = 0,Doesn't Equal = 1,Contains = 2,Doesn't Contain = 3,Begins With = 4,Ends With = 5,Less Than Or Equal To = 6,Less Than = 7,Equal To = 8,Greater Than = 9,Greater Than Or Equal To = 10
ConditionValueStringNOBodyIf condition is text, then a string value is here. If condition is from a picklist: Use REST API: GET Profile Fields to get valid fields. Search for the picklist in result response. Find the desired choice in that picklist. Insert the OptionID here of that choice
GroupNameStringNOBodySpecifies the name of the group for organizing conditions
ParentIDIntegerNOBodySpecifies the parent condition ID for hierarchical condition grouping. The first condition in a group is considered the parent (e.g.,ParentID = 0). Subsequent conditions within the same group must reference their parent (e.g., ParentID = 0).
ActionTypeIntegerNOBody1 = Add to space 3 = Assign site role
ActionValueStringNOBodySpaceID to be added to or removed from

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/personas/188

Request Body

{
  "Name": "Power User"
}

Success Response

{
    "IsError": false,
    "ResponseMessage": "Changes saved successfully",
    "ResponseData": {
        "PersonaID": 188,
        "Name": "Creative Hub",
        "CreatedBy": 1245,
        "UpdatedBy": 1245,
        "DateCreated": "2026-04-03T13:09:20.917",
        "LastUpdated": "2026-04-09T16:42:24.263",
        "IsEnabled": true,
        "IncludeActions": true,
        "PersonaMatchCondition": 0,
        "PersonaConditions": [
            {
                "ConditionID": 265,
                "PersonaID": 188,
                "ProfileFieldID": 267,
                "ConditionValue": "1414",
                "CreatedBy": 1245,
                "UpdatedBy": 1245,
                "LastUpdated": "2026-04-09T16:42:24.45",
                "ConditionOperatorType": 0,
                "ParentID": 0,
                "PersonaMatchCondition": 0,
                "GroupName": "Group A"
            },
            {
                "ConditionID": 266,
                "PersonaID": 188,
                "ProfileFieldID": 266,
                "ConditionValue": "1399",
                "CreatedBy": 1245,
                "UpdatedBy": 1245,
                "LastUpdated": "2026-04-09T16:42:24.45",
                "ConditionOperatorType": 0,
                "ParentID": 0,
                "PersonaMatchCondition": 0,
                "GroupName": "Group B"
            }
        ],
        "PersonaActions": [
            {
                "ActionID": 218,
                "PersonaID": 188,
                "ActionValue": "715",
                "CreatedBy": 1245,
                "UpdatedBy": 1245,
                "LastUpdated": "2026-04-09T16:42:24.45",
                "ActionType": 1,
                "Index": 0
            }
        ],
        "EditAbsoluteURL": "https://your-site.com/personas/addedit/188",
        "DateCreatedString": "6 days ago",
        "LastUpdatedString": "just now",
        "RunActionsOnSave": false,
        "CreatedByUserDisplayName": "Alice Romero",
        "UpdatedByUserDisplayName": "Alice Romero"
    }
}

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. (personaID, persona)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 persona was not found.Verify the personaID 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