How to get Exif and People data on searchMemories API
I’m trying to call the searchMemories API (https://immich.app/docs/api/search-memories). The base request works, I get the list of assets but it’s not returning EXIF or people data for those assets. The docs kind of imply this information might be included, but I doubt it’s loaded by default based on how the other APIs behave.
- My first thought was to use: withExif and withPeople as url params (other api's have it in the post body)
http://10.20.3.10:2283/api/memories?type=on_this_day&withExif=ture&withPeople=true
No luck, this didn't work.
- Just for kicks I passed a request body on the Get request {"withPeople": ture} also with no luck.
My work around is to get the memories then do follow up call for each asset. Not awesome but would work. But before I do that, I wanted to make sure I'm not missing something and it's not user error. lol.
4 Replies
:wave: Hey @asherry99,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Hey!
Exif info and people in API docs for searchMemories:
- marked "optional" in https://immich.app/docs/api/search-memories/
- is not marked "required" in https://api.immich.app/models/AssetResponseDto (linked from https://api.immich.app/endpoints/memories/searchMemories)
They are marked so because they are optional in https://github.com/immich-app/immich/blob/50eae23f3a40d763b4746227a5f63befac8c5214/server/src/dtos/asset-response.dto.ts#L111-L112
So depending on the API, they may or may not be included in response.
Unfortunately memories API do not fetch exif info or people info, see for example https://github.com/immich-app/immich/blob/50eae23f3a40d763b4746227a5f63befac8c5214/server/src/queries/memory.repository.sql#L29-L56 - here is no SQL JOIN with
asset_exif or with asset_face.
Therefore exif and faces do not appear in memory API responses. This is expected behavior, though it forces you to implement that workaround using follow up calls.Ah got it. Thank you for checking and explaining that for me.