API information regarding ManualImport command #4216

New issue

Open

opened 2026-02-20 13:17:39 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 13:17:39 -05:00

Owner

Originally created by @Arturoe1 on GitHub (Nov 14, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

I am trying to use an script to run a manual import for matched items (sometimes lidarr does not import items if there are missing tracks ) so they are imported when using the api/v1/command - Manualimport.

I can see the command is used in the UI but there is no information regarding the payloads. Trace log file which should provide those details unfortunately does not.

However i haven't been able to find documentation about the payload to send. Is it possible to get some information about it?

Describe the solution you'd like

Information about how to call the API to trigger the manual import of the items programatically. If possible to replicate the functionaliy the UI has regarding combining the exisiting files and ignoring the errors.

Describe alternatives you've considered

I have tried looking in internet, checked the API lidarr page but the information there is barebones and does not provide all the info.
Even the trace logs don't provide a lot of detail .

Anything else?

When running the web ui this log is relevant, however it does not provide with the payload details and i cannot find more info.

Originally created by @Arturoe1 on GitHub (Nov 14, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Is your feature request related to a problem? Please describe I am trying to use an script to run a manual import for matched items (sometimes lidarr does not import items if there are missing tracks ) so they are imported when using the api/v1/command - Manualimport. I can see the command is used in the UI but there is no information regarding the payloads. Trace log file which should provide those details unfortunately does not. However i haven't been able to find documentation about the payload to send. Is it possible to get some information about it? ### Describe the solution you'd like Information about how to call the API to trigger the manual import of the items programatically. If possible to replicate the functionaliy the UI has regarding combining the exisiting files and ignoring the errors. ### Describe alternatives you've considered I have tried looking in internet, checked the API lidarr page but the information there is barebones and does not provide all the info. Even the trace logs don't provide a lot of detail . ### Anything else? When running the web ui this log is relevant, however it does not provide with the payload details and i cannot find more info. 025-11-14 14:46:45.0|Trace|CommandQueueManager|Publishing ManualImport 2025-11-14 14:46:45.0|Trace|CommandQueueManager|Checking if command is queued or started: ManualImport 2025-11-14 14:46:45.0|Trace|CommandQueueManager|Inserting new command: ManualImport 2025-11-14 14:46:45.1|Trace|CommandExecutor|ManualImportCommand -> ManualImportService 2025-11-14 14:46:45.1|Trace|CommandQueueManager|Marking command as started: ManualImport 2025-11-14 14:46:45.2|Trace|Http|Res: 2016 [POST] /api/v1/command: 201.Created (119 ms) 2025-11-14 14:46:45.2|Debug|Api|[POST] /api/v1/command: 201.Created (119 ms) 2025-11-14 14:46:45.2|Trace|EventAggregator|Publishing CommandUpdatedEvent 2025-11-14 14:46:45.2|Trace|EventAggregator|CommandUpdatedEvent -> CommandController 2025-11-14 14:46:45.2|Trace|EventAggregator|CommandUpdatedEvent <- CommandController 2025-11-14 14:46:45.2|Trace|ManualImportService|Manually importing 21 files using mode Auto 2025-11-14 14:46:45.2|Trace|EventAggregator|Publishing CommandUpdatedEvent 2025-11-14 14:46:45.2|Trace|EventAggregator|CommandUpdatedEvent -> CommandController 2025-11-14 14:46:45.2|Trace|EventAggregator|CommandUpdatedEvent <- CommandController 2025-11-14 14:46:45.2|Trace|ManualImportService|Processing file 1 of 21 2025-11-14 14:46:45.2|Trace|EventAggregator|Publishing CommandUpdatedEvent 2025-11-14 14:46:45.2|Trace|EventAggregator|CommandUpdatedEvent -> CommandController 2025-11-14 14:46:45.2|Trace|EventAggregator|CommandUpdatedEvent <- CommandController