Closed CanisHelix closed 4 years ago
Hi!
Thanks for the issue report. Before a real human comes by, please make sure you used our bug report format.
Have you looked at the wiki yet? https://github.com/tidusjar/ombi/wiki/
Before posting make sure you also read our FAQ.
Make the title describe your issue. Having 'not working' or 'I get this bug' for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or update the tag and keep you updated.
Thanks!
Ombi Bot.
Swagger for Ombi is used for discovery of the API's id recommend reading the wiki and not using swagger for testing the api's
NOTE when using the API Key then everything is assumed as admin and there is no user associated with it, If you want it to be associated with a user you need to pass an additional header "UserName" with the value being the username of the user. If the username does not exist then the API call will not work.
Running curl -i -X GET -H "accept: application/json" -H "ApiKey: <APIKeyFromUI>" "http://localhost:5000/api/v1/Request/tv"
or curl -i -X GET -H "accept: application/json" -H "ApiKey: <APIKeyFromUI>" "http://localhost:5000/api/v1/Request/movie"
Both respond with the same error
{"error":"Value cannot be null.\nParameter name: user"}
The only way to get these to work is to put in a UserName header of a valid User along with the API. The wiki clearly states it should assume as admin and no user is associated with it.
Swagger is just easier replication steps for you. If you prefer CURL examples instead, then so be it.
I can confirm that, the header need to be edited as well for the post section. There needs to be a filed to enter a UserName.
I'm having this issue as well. I am unable to connect Ombi via API to organizr or grafana to get request lists.
Describe the bug When calling either
/api/v1/Request/tv
orapi/v1/Request/movie
to get a list of request using an ApiKey, the result is a failure.To Reproduce Steps to reproduce the behavior:
/swagger/index.html
/api/v1/Request/tv
Try it out
Expected behavior A 200 response with JSON output as documented.
Logs (Logs directory where Ombi is located)
Desktop (please complete the following information):
Ombi Version (please complete the following information):
Additional context Can be resolved by adding
UserName:
to the header before calling API from application. Doesn't work from swagger though.