In this article, you can read about the common data types and formats used across the RecMan API. Understanding these shared conventions will help you interpret and construct requests consistently across all scopes.
Date and Date-Time Formats
Fields that represent a date or a date combined with a time follow one of the two formats below, depending on the field.
| Format name | Pattern | Example |
|---|---|---|
| Date | YYYY-MM-DD | 2026-01-15 |
| Date-time | YYYY-MM-DD HH:MM:SS | 2026-01-15 14:30:00 |
Note
Always check the field description in the relevant endpoint's parameter table to confirm whether a date or a date-time value is expected, as the required format differs per field.
Country and Language Codes
Fields referring to a country or a language use standardized two-letter codes rather than full names.
| Code type | Standard | Example |
|---|---|---|
| Country code | ISO 3166-1 Alpha-2 | NO, SE, DK, GB |
| Language code | ISO 639-1 | en, no, sv, da |
ID Fields and Arrays of IDs
Most entities are referenced by their integer ID. Some fields accept a single ID, while others accept an array of IDs to link multiple related records in one request.
| Field | Type | Required | Description |
|---|---|---|---|
| id | integer | Varies | Unique identifier of a single related record. |
| ids | array of integers | Varies | List of unique identifiers used to link or filter multiple related records in a single request. |
Boolean Values
Boolean fields indicate a true/false state. Refer to each endpoint's parameter table for the specific field, since some accept a native boolean while others expect an integer flag.
File Upload Fields
Endpoints that support uploading a file (such as candidate certifications, interview files, or reference check files) expect the file content to be base64-encoded and submitted together with a filename.
| Field | Type | Required | Description |
|---|---|---|---|
| fileName | string | Required | Name of the file, including its extension. |
| file | string (base64) | Required | Base64-encoded content of the file. |
Note
Field names for file uploads can vary slightly between scopes (for example, candidate certification files vs. reference check files). Always refer to the specific endpoint's parameter table for the exact field name expected.