Skip to main content

​
What is Mais Hábito?

Mais Hábito is a gamified habit-tracking backend REST API that helps users build better routines through a points and streaks reward system. As a single-player application, it lets users organize their daily routine by completing tasks and challenges — earning points and XP along the way, and maintaining streaks to track consistency over time. The API is built for developers who want a fully-featured backend for productivity or habit-tracking applications, with authentication, user profiles, challenge management, and task completion already handled.

​
Tech stack

TechnologyRole
Node.js 20+JavaScript runtime
TypeScript 5.9Typed superset of JavaScript
Express 5HTTP server and routing framework
PostgreSQL 16Relational database
Knex.jsQuery builder and database migrations
JWT (jsonwebtoken)Stateless authentication tokens
bcryptPassword hashing
node-cronScheduled jobs (streak reset calculations)
cors / dotenvNetwork security and environment configuration

​
Resource groups

The API exposes six resource groups under the base URL http://localhost:3000/api:
Route prefixDescription
/api/authAccount creation and login
/api/userUser profile read and update
/api/challenge-templatesChallenge catalog — CRUD for challenge models
/api/user-challengesAccept, complete, abandon, or annotate active challenges
/api/tasksDaily and one-off task management (CRUD)
/api/task-completionsMark tasks complete — primary mechanism for earning XP and points

​
Architecture

The project follows a Controller → Service → Repository layered pattern: 
HTTP Request
     │
     ▼
  Router          — Maps endpoints to controller methods
     │
     ▼
  Middleware      — authMiddleware validates Bearer token; errorHandler normalises errors
     │
     ▼
  Controller      — Reads req/res, extracts payload, delegates to service
     │
     ▼
  Service         — Business logic: validation, gamification rules, streak calculation
     │
     ▼
  Repository      — Raw Knex.js queries; the only layer that talks to PostgreSQL
     │
     ▼
  PostgreSQL      — Persistent storage
This separation means database internals are hidden behind repositories, business rules are tested independently in services, and controllers stay thin and focused on HTTP concerns.

​
Get started

Quickstart

Get the API running locally in under 5 minutes.

Authentication

Learn how JWT authentication works and how to call protected endpoints.

Build docs developers (and LLMs) love

Get started for freeTalk to us