Fetch a specific institution member by their unique identifier. This endpoint allows you to retrieve detailed information about a single user belonging to your institution.
User Access:
Validation:
HMAC signature authentication. The Authorization header must contain your public key
and HMAC signature in the format: public_key:signature
Format: Authorization: public_key:signature
Example: Authorization: pub_abc123xyz:abc123def456ghi789...
The signature is generated by creating an HMAC hash of the request body (JSON stringified) using your secret key for POST/PUT requests. For GET requests, the signature is generated using the query parameters (JSON stringified) instead of the request body. Contact your account manager to obtain your public key and secret key for generating signatures.
Unique identifier of the user to fetch
User fetched successfully
User information
Unique identifier of the user
"550e8400-e29b-41d4-a716-446655440000"
User's first name
"John"
User's last name
"Doe"
User's middle name or other name
"Michael"
User's email address
"john.doe@example.com"
User's gender
"male"
User's date of birth
"2026-04-01T10:09:09.886Z"
KYC details for the user
User's mobile phone number
"+233241234567"
User's Ghana Card number
"GHA-123456789-1"
URL of the user's Ghana Card image
"https://example.com/images/ghana-card.jpg"
URL of the user's profile image
"https://example.com/images/user-profile.jpg"
Whether the user's Ghana Card has been verified
true
List of document identifiers or URLs
["document1.pdf"]User's account details (Mobile Money or Bank account)
Date and time when the user was created
"2026-04-01T10:09:09.886Z"