Skip to content

docs: add API endpoint documentation#66

Open
jayati04 wants to merge 1 commit into
alphaonelabs:mainfrom
jayati04:docs/api-endpoints
Open

docs: add API endpoint documentation#66
jayati04 wants to merge 1 commit into
alphaonelabs:mainfrom
jayati04:docs/api-endpoints

Conversation

@jayati04

@jayati04 jayati04 commented Jun 9, 2026

Copy link
Copy Markdown

Summary

This PR adds API endpoint documentation to the README.

Changes

  • Added authentication endpoint documentation
  • Added activity management endpoint documentation
  • Added dashboard endpoint documentation

Motivation

The backend exposes several API routes through the Cloudflare Worker, but these routes were not documented in the README. This change improves onboarding for contributors and developers by providing a quick reference for commonly used endpoints.

Updated the README with an API Endpoints reference covering authentication, activity management, and dashboard routes. This improves developer onboarding and clarifies the backend endpoints exposed through the Cloudflare Worker without changing functionality.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

The README now includes an “API Endpoints” section documenting Authentication, Activities, and Dashboard routes with their HTTP methods and descriptions.

Changes

API endpoint documentation

Layer / File(s) Summary
Endpoint reference
README.md
Adds tables documenting registration, login, activity listing and detail, activity joining, and dashboard endpoints.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the change, describing added API endpoint documentation in the README.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@A1L13N

A1L13N commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai please review this

@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

@A1L13N I’ll review the API documentation updates for accuracy, clarity, and onboarding usefulness.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 149-150: Update README.md formatting by adding a blank line
between the closing code fence and the “## API Endpoints” heading, and ensure
the file ends with exactly one trailing newline.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: alphaonelabs/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: aae12dce-635b-40f9-954e-4b8e4a79e30c

📥 Commits

Reviewing files that changed from the base of the PR and between 997b01e and 838843e.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment on lines +149 to +150
```
## API Endpoints

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix the Markdown spacing and trailing newline.

Add a blank line between the closing code fence and ## API Endpoints, and ensure the file ends with exactly one newline so markdownlint passes.

Also applies to: 172-172

🧰 Tools
🪛 markdownlint-cli2 (0.23.0)

[warning] 149-149: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


[warning] 150-150: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Above

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 149 - 150, Update README.md formatting by adding a
blank line between the closing code fence and the “## API Endpoints” heading,
and ensure the file ends with exactly one trailing newline.

Source: Linters/SAST tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants