When creating or updating members through Raklet’s API, some fields (like gender, bloodType, maritalStatus, etc.) require specific predefined values. These values are managed through Select Lists, and you can retrieve them dynamically via the SelectList API.
🔍 What is the SelectList API?
The SelectList API provides the full list of acceptable options for fields that use ENUM-type values in Raklet.
This helps ensure you’re always using valid values and prevents common 400 errors from invalid ENUMs.
Endpoint | Description | Use In |
GET /common/genders | Returns gender options | gender field in member creation |
GET /common/bloodTypes | Returns blood type options | bloodType field |
GET /common/maritalStatusTypes | Returns marital status options | maritalStatus field |
GET /common/educationLevels | Returns education level options | Custom fields or user profiles |
GET /common/jobTypes | Returns job type options | lookingForAJobType or job-related fields |
GET /common/languages | Returns supported languages | language field in member creation |
GET /common/countryCodes | Returns international phone dialing codes | phoneCountryCode field |
GET /common/countries | Returns list of countries | birthPlace, nationality, or address fields |
GET /common/states | Returns list of states/provinces (usually based on country context) | Address or location fields |
GET /common/months | Returns months of the year | Birthdate fields, reporting filters |
GET /common/years | Returns a list of years | Birth year, graduation year, etc. |
Each of these endpoints returns an array of objects with at least a name property. Use the name values as ENUM strings when passing data into API requests (e.g. "Male", "Single", "RhNegativeA").
🧪 Example Request: Fetch Genders
curl -X GET https://api.raklet.com/common/genders \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
📥 Example Response
[
{
"id": 1,
"name": "NoEntry"
},
{
"id": 2,
"name": "Male"
},
{
"id": 3,
"name": "Female"
}
]
Always use the "name" value (e.g., "Male", "Female") in your API payloads — not the numeric ID.
✅ Example: Using ENUMs in a Member Request
{
"firstName": "Michael",
"lastName": "Jackson",
"emailAddress": "[email protected]",
"gender": "Male",
"bloodType": "RhPositiveA",
"maritalStatus": "Single",
"isTermsOfUseAccepted": true
}💡 Pro Tip
Always fetch ENUM values dynamically if you’re building a form or automation.
Don’t rely on label names — always use the value field returned by the SelectList API.