BroomJack
commented
2 years ago It has been decided that with our new endpoints we will make sure they return the same style response as the original endpoints in order to make the transition seamless. Therefore the decision to drop the active field will instead be implemented at a later date and the response has been altered to make this endpoint work again. Pull request closed as a result.
In this request I fix issue #29 by just removing the active field from the resource so it doesn't validate against it. This will allow for the endpoint to work in staging where the value isn't passed and it will continue to work in production as it won't fail when this value is passed unexpectedly.