Returns an employee photo at the requested size. Available sizes are: original (full resolution), large (340×340), medium (170×170), small (150×150), xs (50×50), and tiny (20×20). The response shape is selected via standard HTTP content negotiation: by default the body is the stored image bytes and the Content-Type response header matches the body (image/jpeg, image/png, image/bmp, image/gif, or image/tiff). When the caller sends Accept: application/json (typical MCP/LLM-connector usage), the body is a JSON object { mimeType, fileBase64 } with the same image bytes base64-encoded, and the response Content-Type is application/json.
A 404 response covers three distinct cases: (1) the employee exists but has no photo on file (a normal, non-error state), (2) the employee ID does not exist, or (3) the size value is not one of the recognized options. The x-bamboohr-error-message response header distinguishes them: Employee photo not found, Employee not found, or Size: "<value>" is not a valid size option. Valid sizes are: xs, small, tiny, original, medium and large.. Treat "Employee photo not found" as a normal "no photo on file" result rather than as a bad employee ID, permission failure, or other error to debug.
OAuth Scopes: employee:photo
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Description
Returns the binary data for the employee photo.
Notes
Content type "image/jpeg".
| Size | Dimensions |
|---|---|
| original | Uploaded size* |
| large | 340 x 340 |
| medium | 170 x 170 |
| small | 150 x 150 |
| xs | 50 x 50 |
| tiny | 20 x 20 |
*Keep in mind that although the api has an upload limit of 20MB the UI has a limit of 600x600 px. So sizes may not match what was uploaded from the UI but they will match with what was uploaded on the store a new employee photo endpoint.
The authenticated user does not have permission to view this employee's photo.