This repository was archived by the owner on Sep 2, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 2, 2020. It is now read-only.
HTTP 405, Method Not Allowed, when listing badge instances #74
Description
According to the API documentation, the server should accept GET /systems/:slug/badges/:slug/instances - I assume this would get a list of instances of the badge. However, when I access that endpoint, I get HTTP 405 and a MethodNotAllowedError.
The specific request I'm making on my system is GET http://localhost:8080/systems/badgekit/badges/excellent-badge/instances; excellent-badge is a badge that exists.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Activity
SueSmith commentedon Apr 22, 2014
Hello, I can't help with the 405 error, hopefully one of the Open Badges devs will follow up on that..! Just to clarify and in case it helps, badge instances are instances of the badge that have been awarded to an earner, so this may be an empty data set (might be worth checking the badgeInstances table in your database). To retrieve the data for the badge itself, removing the
/instancesfrom your request should work..tgs commentedon Apr 22, 2014
Thanks! Yeah, I just checked and it still returns 405 whether there's any rows in the badgeInstances table or not.
SueSmith commentedon Apr 22, 2014
Ah thanks for following up, I'm not too familiar with what happens in the data when a badge is issued (and badgeInstances are created) so am not much help but I'm sure someone will get back to you on this soon!
threeqube commentedon Apr 22, 2014
@cmcavoy can we look into this please?
SueSmith commentedon Apr 23, 2014
Hi @tgs - just a little more info. If you're using the openbadges-badgekit app it has now been updated to implement issuing, so you can issue badges in there (and create badgeInstances in the API). However, I'm still getting the "Method not allowed" error so am thinking this endpoint may just not have been implemented yet - will try to find out more today and give you an update!
andrewhayward commentedon Apr 23, 2014
Just to add to the confusion, I have a feeling it's a case of the docs being wrong. However, it's definitely an issue for @brianloveswords to weigh in on.
cmcavoy commentedon Apr 23, 2014
@tgs I know we talked about this IRL, but can you write up how you want to use that endpoint? I think there's some questions about whether or not the endpoint is a good idea.
tcst commentedon Apr 23, 2014
I share the same use cases as well.
As an earner, I would like to see the people that earn the same badge that I earned/or going to apply for, in order to network with them, asking them about the experience of getting this badge, or explore new opportunities. Since those people are interested in the same badge, they must have share the same habit/experience/skill set and will be more likely the type of people I want to network.
Also looking at the list of the earners, I can tell how valuable the badge is.
As an employer, I can look into the list of the earner for a badge (specific skills) and find the potential candidate for the position I'm trying to fill.
There's more, but I believe this API is very useful to have.
Thanks,
Vu
cmcavoy commentedon Apr 23, 2014
I think the most immediate need for it is to get aggregate issued counts into the BadgeKit front end. I'm going to give this one the 👍 and say we should implement it asap. We'll get on it.
mbad0la commentedon Nov 8, 2015
Is this error because of the fact that you're not listening for a 'GET' request on the mentioned endpoint?
Please confirm.