Security profiles in domain (requires LIST^PROFILE)
GET /v1/profiles
Operation id: v1Profiles
Description
Domain header note: if x-reflexis-domain-x is provided it must match the token's domain, otherwise 401. Same restriction as user-details.
Tags: Kernel NextGen APIs
Parameters
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
auth_token | string | No | |
org_level | integer | No | |
product_id | string | No | Optional — return only profiles licensed for this product id |
Header parameters
| Name | Type | Required | Description |
|---|---|---|---|
x-reflexis-auth-token-x | string | No | Authentication token (or use auth_token query param) |
x-reflexis-domain-x | string | No | Domain id string; optional — defaults to token domain |
Responses
200 — OK — list envelope; data is profile detail objects (sorted by seq / name). has_more is always false (no pagination).
Content type: application/json
401 — Authentication failed. The request is missing a token, the token is invalid, or the token has expired.
Content type: application/json
403 — User lacks the required permission for this operation.
Content type: application/json
500 — An unexpected error occurred while processing the request.
Content type: application/json
Response models
200 — OK — list envelope; data is profile detail objects (sorted by seq / name). has_more is always false (no pagination).
Content type: application/json
Schema
List envelope whose data entries are domain security profile details
| Property | Type | Required | Description |
|---|---|---|---|
object | string | No | |
url | string | No | |
data | array | No | |
has_more | boolean | No | |
next_cursor | string, nullable | No | |
fetched_at | string (date-time) | No |
{
"type": "object",
"description": "List envelope whose data entries are domain security profile details",
"properties": {
"object": {
"type": "string",
"example": "list"
},
"url": {
"type": "string"
},
"data": {
"type": "array",
"items": {
"type": "object",
"description": "Security profile for the domain. Additional fields may be present; shape follows server-defined profile maps.\n",
"properties": {
"profileId": {
"type": "string"
},
"profileName": {
"type": "string"
},
"domainNo": {
"type": "integer"
},
"orgLevel": {
"type": "integer"
},
"organizationLevel": {
"type": "string"
},
"seqNo": {
"type": "integer"
},
"sequenceNo": {
"type": "integer"
}
}
}
},
"has_more": {
"type": "boolean"
},
"next_cursor": {
"type": "string",
"nullable": true
},
"fetched_at": {
"type": "string",
"format": "date-time"
}
}
}
401 — Authentication failed. The request is missing a token, the token is invalid, or the token has expired.
Content type: application/json
Schema
Structured error envelope returned by external gateway endpoints (/v1/api/*). Wraps a single error object with type, code, human-readable message, the offending param (when applicable), and an optional documentation URL.
| Property | Type | Required | Description |
|---|---|---|---|
error | object | No |
{
"type": "object",
"description": "Structured error envelope returned by external gateway endpoints (`/v1/api/*`).\nWraps a single `error` object with `type`, `code`, human-readable `message`, the offending\n`param` (when applicable), and an optional documentation URL.\n",
"properties": {
"error": {
"type": "object",
"properties": {
"type": {
"type": "string",
"description": "High-level error category (for example `unauthorized`, `invalid_parameter`, `validation_error`).",
"example": "invalid_parameter"
},
"code": {
"type": "string",
"description": "Machine-readable error code; clients should branch on this rather than `message`.",
"example": "invalid_parameter"
},
"message": {
"type": "string",
"description": "Human-readable description of the error.",
"example": "One or more request parameters are invalid."
},
"param": {
"type": "string",
"description": "Name of the request parameter or field that caused the error, when applicable.",
"example": "page_number",
"nullable": true
},
"doc_url": {
"type": "string",
"description": "Optional URL to documentation describing the error.",
"example": "https://{APP_URL}/kernel/errors/invalid_parameter",
"nullable": true
}
}
}
}
}
403 — User lacks the required permission for this operation.
Content type: application/json
Schema
Structured error envelope returned by external gateway endpoints (/v1/api/*). Wraps a single error object with type, code, human-readable message, the offending param (when applicable), and an optional documentation URL.
| Property | Type | Required | Description |
|---|---|---|---|
error | object | No |
{
"type": "object",
"description": "Structured error envelope returned by external gateway endpoints (`/v1/api/*`).\nWraps a single `error` object with `type`, `code`, human-readable `message`, the offending\n`param` (when applicable), and an optional documentation URL.\n",
"properties": {
"error": {
"type": "object",
"properties": {
"type": {
"type": "string",
"description": "High-level error category (for example `unauthorized`, `invalid_parameter`, `validation_error`).",
"example": "invalid_parameter"
},
"code": {
"type": "string",
"description": "Machine-readable error code; clients should branch on this rather than `message`.",
"example": "invalid_parameter"
},
"message": {
"type": "string",
"description": "Human-readable description of the error.",
"example": "One or more request parameters are invalid."
},
"param": {
"type": "string",
"description": "Name of the request parameter or field that caused the error, when applicable.",
"example": "page_number",
"nullable": true
},
"doc_url": {
"type": "string",
"description": "Optional URL to documentation describing the error.",
"example": "https://{APP_URL}/kernel/errors/invalid_parameter",
"nullable": true
}
}
}
}
}
500 — An unexpected error occurred while processing the request.
Content type: application/json
Schema
Structured error envelope returned by external gateway endpoints (/v1/api/*). Wraps a single error object with type, code, human-readable message, the offending param (when applicable), and an optional documentation URL.
| Property | Type | Required | Description |
|---|---|---|---|
error | object | No |
{
"type": "object",
"description": "Structured error envelope returned by external gateway endpoints (`/v1/api/*`).\nWraps a single `error` object with `type`, `code`, human-readable `message`, the offending\n`param` (when applicable), and an optional documentation URL.\n",
"properties": {
"error": {
"type": "object",
"properties": {
"type": {
"type": "string",
"description": "High-level error category (for example `unauthorized`, `invalid_parameter`, `validation_error`).",
"example": "invalid_parameter"
},
"code": {
"type": "string",
"description": "Machine-readable error code; clients should branch on this rather than `message`.",
"example": "invalid_parameter"
},
"message": {
"type": "string",
"description": "Human-readable description of the error.",
"example": "One or more request parameters are invalid."
},
"param": {
"type": "string",
"description": "Name of the request parameter or field that caused the error, when applicable.",
"example": "page_number",
"nullable": true
},
"doc_url": {
"type": "string",
"description": "Optional URL to documentation describing the error.",
"example": "https://{APP_URL}/kernel/errors/invalid_parameter",
"nullable": true
}
}
}
}
}