• https://documenter.getpostman.com/view/5211679/SVYwLwLL

• https://sterling-league-test.herokuapp.com/api/v1/
• Please refer to the documentation link above for a full list of all the endpoints

• The rate limit is setup with redis on heroku
• Only the public API has throttle limit set. The Admin API has no throttle limit
• The Authentication Endpoints do not have any rate limits
• On the public route only 12 API calls are allowed per minute

After signup/signin a JWT will be passed in the body. When making requests to the protected endpoints, add the token in the Authorization header in the format Bearer token

Create a API that serves the latest scores of fixtures of matches in a “Mock Premier League”

There should be:

• Admin accounts which are used to
  • signup/login
  • manage teams (add, remove, edit, view)
  • create fixtures (add, remove, edit, view)
  • Generate unique links for fixture
• Users accounts who can
  • signup/login
  • view teams
  • view completed fixtures
  • view pending fixtures
  • robustly search fixtures/teams
• Only the search API should be availble to the public.

1. Use redis as your session store.
2. Authentication and Authorization for admin and user accounts should be done using Bearer token and JWT.

• NodeJs (JavaScript or TypeScript)
• MongoDB
• Redis
• Docker
• POSTMAN
• Jest
• Express

Unit tests are a must, submissions without tests will be ignored.

1. Your API endpoints should be documented in POSTMAN.
2. Seed the db with lots of data before final submission.
3. Code should be hosted on a git repository, Github preferably.
4. The API should be hosted on a live server (e.g. https://heroku.com)

You'll get bonus points for:

1. containerization using docker.
2. Thorough documentation using POSTMAN.
3. e2e tests and use of Jest for tests.
4. web caching API endpoints using Redis.
5. Implementing rate limiting for user account API access.

7 days

Please send an email to acknowledge the receipt of this document.