Boromir API Bugs or outdated Documentation
Boromir API Bugs or outdated Documentation
This is the behavior I have noticed when testing the Boromir API: when using a valid user token to test the API in the swagger-documentation testing interface, the article endpoint returns a 401 error. This also happens when I make the curl request myself. I think this may be due to a mismatch in the swagger-documentation and the current state of authentication. Is it, perhaps, no longer possible to use the API with just the user token and an application key has to be generated and passed through the header to pass authentication? when using the image endpoint in the swagger-documentation testing interface, or sinding the curl request manually, the endpoint returns a 500 server error.
Steps to Reproduce
Go to the Swagger Documentation, authorize with a valid user token, then test the article and image endpoint with valid article and image ids respectively.
Operating System
LinuxBrowser
FirefoxRelated Entity
The Boromir APIHistory
Hey, I cannot reproduce the 401 error when using the Swagger Documentation interface (I also tested on Postman, which is another API testing application) so it might be an issue with the authentication tokens you're using or the article/image id.
You can head to the discord's API help channel for further help!
Find your way!
Resources
WHO WE ARE
LEGAL
Listen to our Podcast
