Additional info API call from TVMaze: Use the ?moreDetail=true query param on the show/:id endpoint to get more detail about the show.

Multi-tiered user authentication:

• User permissions object generated from maturity settings, subscription type, and user type.
• Preliminary calls are made before each request with no filtering applied, filters are then validated against the response to let the user know why they can't access a specific resource.
• User types are admin/user/child. Each user/child has an admin ID, tying them to an admin user. An admin can edit their sub-users (apart from changing key features like their admin ID or subscription type), and deleting themselves will cascade the delete to also remove their sub-users.
• Only the above types have been faked, but another valid type 'database_admin' exists. This user is permitted to create, update, and delete Title listings.

User favourites: Each user has a favourites list tied to object IDs. This list can be populated when viewing users using the ?populate=my_list query param on the /manageProfiles endpoint.

User avatars: Similar to above, each user has an avatar ID tied to an avatar object. Use ?populate=avatars to populate with their real values when viewing users

Automated seeding:

• Mongoose schema converted to JSON schema using mongoose-schema-jsonschema. Fake data then generated using json-schema-faker.
• Use npm run seed to generate 10 Avatars and 100 Users, with object references between the two, and references to real Title objects in each user's 'my_list'.
• A subset of users will be admins. Between the admins and sub-users are real object references using the 'admin_id' field.

A search key has been added to the database, enabling fuzzy search on the /title/:title and /show/:show endpoints. The latter also accepts IMDB IDs, which are validated.

Sort by, sort direction, and limit query params may be applied to all Title endpoints excluding /id/:id.

Stripe integration - When registering a new user, stripe customer and charge objects are generated, the correct fee is charged depending on the type of subscription the user has chosen, and stripe details are applied to the user object. The transaction is saved to my Stripe account, appearing on the dashboard.

Avatar images hosted on S3 bucket.