Boromir API Bugs or outdated Documentation

Closed

Feature: API
Reported by: IsaNite
Opened: 7 Jul 2026
Assigned to: katerinach
Last activity: 87 days ago

Not a Bug

Description

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.

History

Comments and updates to this report

7 Jul 2026 · 15:07

katerinach Assignee

Assigned katerinach

20 Jul 2026 · 10:54

0nnia Moderator

Added tag Not a Bug

20 Jul 2026 · 11:13

katerinach Assignee

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!