GET /api/profile/me

The Profile endpoints give you full read and write access to the authenticated user’s account data. You can retrieve the complete profile snapshot — including trust level, accuracy scores, streak, and preferences — or update individual fields. All endpoints in this section require an active session.

Retrieve the current user’s profile, stats, and account preferences in a single call.

GET /api/profile/me

Authentication: Required

Response fields

object

The authenticated user’s full profile record.

Show Profile fields

string

The user’s UUID. Use this as a stable identifier — usernames can change.

string

The user’s public username, unique across PRIXO.

string

The user’s chosen display name shown in the UI and on the leaderboard.

string

URL of the user’s avatar image.

string

Short user-authored bio text.

string

The user’s primary area in Arabic, used for leaderboard and scope resolution, e.g. العليا.

number

Total number of accepted price contributions by this user.

number

Current redeemable points balance.

object

The user’s current trust level.

Show Trust level fields

string

Internal identifier for the trust level, e.g. saane.

string

Trust level name in Arabic, e.g. سنع.

string

Trust level name in English, e.g. Saane.

string

Emoji icon, e.g. 🏅.

number

The weight applied to this user’s price confirmations relative to newer contributors. Higher levels carry more weight.

number

An overall trust score from 0–100 reflecting the user’s confirmation accuracy and engagement history.

number

Percentage of the user’s price submissions that were subsequently confirmed as accurate by the community.

number

Number of consecutive days the user has contributed or confirmed at least one price. Resets to 0 if a day is missed.

object

The user’s current account preferences.

Show Preferences fields

string

The UI language preference. See supported values below.

boolean

When true, the user’s profile is publicly visible via the leaderboard and other community features.

boolean

When true, the user appears in leaderboard results. Requires show_public_profile to also be true.

Example response

{
  "profile": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "username": "myusername",
    "display_name": "My Name",
    "avatar_url": "https://cdn.prixo.ai/avatars/myusername.jpg",
    "bio": "Love food in Riyadh",
    "area": "العليا",
    "contribution_count": 42,
    "points_balance": 1200,
    "trust_level": {
      "slug": "saane",
      "name_ar": "سنع",
      "name_en": "Saane",
      "icon": "🏅",
      "confirmation_weight": 2
    },
    "trust_score": 85,
    "accuracy_score": 92,
    "streak_days": 7
  },
  "preferences": {
    "language": "ar",
    "show_public_profile": true,
    "show_in_leaderboard": false
  }
}

PATCH /api/profile/me

Update writable fields on the authenticated user’s profile.

PATCH /api/profile/me

Authentication: Required

Updatable fields

string

The user’s display name shown publicly.

string

The user’s unique username. Must be URL-safe and unique across PRIXO.

string

Short bio text.

string

Primary area in Arabic, used for leaderboard scope and location-aware features.

boolean

Set to true to make the profile visible in community features and the leaderboard.

boolean

Control whether the user appears in public leaderboard results. Has no effect if show_public_profile is false.

string

Preferred UI language. See supported values below.

Language values

The language preference field accepts the following values:

Value	Language
`auto`	Detect from browser or device
`ar`	Arabic
`en`	English
`ur`	Urdu
`hi`	Hindi
`tl`	Filipino (Tagalog)

POST /api/feedback

The feedback endpoint lets your integration — or the PRIXO in-app widget — submit user feedback directly to the PRIXO team.

POST /api/feedback

Authentication: Required Rate limit: 3 requests per minute per user

Exceeding the rate limit returns 429 Too Many Requests. Space out feedback submissions — this endpoint is designed for deliberate user-triggered actions, not automated bulk submissions.

Request body

string

required

The feedback message text. Plain text only.

string

An optional category tag to route the feedback. Example values: bug, suggestion, pricing.

Example request

POST /api/feedback
Content-Type: application/json

{
  "message": "The price comparison for shawarma in Al-Olaya seems outdated.",
  "category": "pricing"
}

Example response

{
  "success": true,
  "id": "fb_7e3a1c09-2d4f-4b8e-a312-0f5c9d7e1b2a"
}

Response fields

boolean

true when the feedback was accepted and queued for review.

string

A unique identifier for the submitted feedback record, prefixed with fb_. You can display this to users as a reference number.

Show the returned id to users after submission so they have a reference if they follow up via support channels.

Overview

Endpoints

GET /api/profile/me — current user profile and stats