Skip to main content
GET
/
v1
/
user
/
me
curl --request GET \
  --url https://api.paypulse.io/v1/user/me \
  --header 'Authorization: Bearer <token>'
{
  "message": "User profile retrieved successfully",
  "code": 200,
  "data": {
    "name": "Jane Doe",
    "email": "jane@example.com",
    "created_on": "2024-03-15",
    "gmail_account_connected": true
  }
}

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/azfar-imtiaz/PayPulse-Cloud/llms.txt

Use this file to discover all available pages before exploring further.

Authentication

All requests to this endpoint must include a valid JWT in the Authorization header.
Authorization: Bearer <token>

Response

message
string
A human-readable confirmation message. Example: "User profile retrieved successfully"
code
number
HTTP status code. 200 on success.
data
object

Error responses

StatusError codeDescription
401INVALID_CREDENTIALSThe Authorization header is missing or the token is invalid.
401TOKEN_EXPIREDThe JWT has expired.
404USER_NOT_FOUNDNo account exists for the user ID encoded in the token.
502DEPENDENCY_FAILUREA downstream dependency (DynamoDB or Secrets Manager) returned an error.
500INTERNAL_SERVER_ERRORAn unexpected server-side error occurred.
Error responses follow this structure:
{
  "error": {
    "code": "USER_NOT_FOUND",
    "message": "User not found"
  }
}
curl --request GET \
  --url https://api.paypulse.io/v1/user/me \
  --header 'Authorization: Bearer <token>'
{
  "message": "User profile retrieved successfully",
  "code": 200,
  "data": {
    "name": "Jane Doe",
    "email": "jane@example.com",
    "created_on": "2024-03-15",
    "gmail_account_connected": true
  }
}

Build docs developers (and LLMs) love