Create User Portal Config
Create a new Portal Config record.
Optional fields
Any request field marked nullable in the schema may be omitted
from the payload entirely - you don't need to send it as null. On a
PATCH (partial update), an omitted field is left unchanged; on a POST
it's left unset.
HTTP Request
POST/users/api/v1/portal-configs/
Example Response
{"id": 0,"site": 0,"branch": 0,"portal": 0,"created": "2026-09-08T14:40:49.611Z","modified": "2026-09-08T14:40:49.611Z","deleted": "2026-09-08T14:40:49.611Z","uuid": "770bba28-9f80-4d40-9c51-6e022364af91","source_ref": "string","active": false,"reference": "string","last_log": -2147483648,"last_message": "string","feed_status": "string","on_portal": false,"agent": 0,"statistics": 0}
| Name | Description |
|---|---|
id | integer ID |
site | integer Site |
branch requirednullable | integer Branch |
portal requirednullable | integer Portal |
created | string Created |
modified | string Modified |
deleted nullable | string Deleted |
uuid | string Uuid |
source_ref nullable | string<= 100 characters Source ref - A unique reference to use for linking records back to *your* system. NB: This must be unique across the entire Prop Data system, so it's best to use a consistent prefix unique to your integration to avoid conflicts with other api consumers. |
active | boolean Active |
reference nullable | string<= 40 characters Reference |
last_log nullable | integer Last log |
last_message nullable | string<= 200 characters Last message |
feed_status nullable | string Feed statusChoices: pendingwithdrawnsuccessfaileddisabled |
on_portal | boolean On portal |
agent required | integer Agent |
statistics nullable | integer Statistics |
Responses
201
400 Bad request body
403 You do not have permission to perform this action
500 Internal server error
503 This website is not active