---
title: "REST API: Get User Profile Fields"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2019-02-28T23:31:46Z
updated: 2026-02-23T03:31:40Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/30567/rest-api-get-user-s-profile-fields"
---

# REST API: Get User Profile Fields

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=30567)
GET/api/content/\{UserID\}

Enables administrators and developers to programmatically retrieve user profile fields for a particular user.

## Request

### Request Header
| Header | Required | Value | Description |
| :--- | :--- | :--- | :--- |
| `Authorization` | YES | `Bearer YOUR_TOKEN` | Bearer token for the authenticated user. [Learn how to create Bearer tokens](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens). |
### Required Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `UserID` | Integer | YES | Path | Unique identifier for a particular user |
| `ContentTypeID` | Integer | YES | Query | The content type ID for User is 15 and it is constant |
| `Fields` | String | YES | Query | A CSV list of the field labels. The field labels are case sensitive. |
## Example

### Request Header

```
Authorization: Bearer YOUR_TOKEN
```

### Request URL

`https://your-site.com/api/content/376?ContentTypeID=123&Fields=string`

### Success Response

```
{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": {
    "Company": "Axero Solutions",
    "Occupation": "HR Manager",
    "Department": "Human Resources",
    "Reports to": "12"
  }
}
```

### Error Response

```
{
  "IsError": true,
  "ResponseMessage": "Required parameter is missing or invalid.",
  "ResponseData": null
}
```

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | One or more required fields are missing or invalid. \(contentID\) | Verify the request payload against the required parameters. |
| 401 Unauthorized | Missing or invalid Bearer token. | Check token validity. [Learn how to create Bearer tokens →](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens) |
| 403 Forbidden | User does not have sufficient permissions. | Confirm the user has the required roles for this action. |
| 404 Not Found | The specified file was not found. | Verify the fileID is correct. |
| 500 Server Error | Internal 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.