Dashboard APIs: seller and investor aggregates

[Jayrodri088]

Context

Sellers need visibility into listings and cash timing; investors need portfolio and exposure views. Dashboard endpoints aggregate Postgres data efficiently for the app UI.

Contributor workflow

• Apply on Drips before opening a PR: Claim this issue through the Drips platform before you open a pull request. Unsolicited PRs from unassigned contributors may be closed without review.
• ETA required: Your application must include an ETA for when you will open the first draft PR.
• Draft PR within 24 hours: If a draft PR is not linked on this issue within 24 hours of assignment, maintainers may unassign you so someone else can take the issue.

Goals

• GET /api/v1/dashboard/seller — aggregates for the authenticated seller, e.g. counts by invoice status, total funded volume, upcoming due dates (define exact metrics in PR).
• GET /api/v1/dashboard/investor — aggregates for the authenticated investor, e.g. active investments, expected return sums, upcoming maturities.
• Use QueryBuilder or SQL with proper indexing awareness; avoid N+1 queries.
• Respect soft deletes and tenant scoping (user can only see their own data).

Out of scope

• Real-time websockets (future).
• On-chain portfolio valuation (future).

Acceptance criteria

• Both endpoints require auth and never leak other users’ aggregates.
• Responses use the standard API envelope.
• Tests with seeded fixtures validate at least one metric calculation.
• npm run type-check passes; tests pass.

PR submission requirements

• CI: All GitHub Actions workflow runs for this PR must pass (green) before merge; failing checks block merge.
• PR description must include: Closes #12.
• PR lists each returned metric with a one-line definition (how computed).
• Note any intentional v1 limitations.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[engr-shalom]

@engr-shalom has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi StellarState team,

I’d like to take on this issue.

I’ll implement request observability with correlation IDs and Prometheus metrics by:

Generating or propagating X-Request-Id and attaching it to all Winston logs per request lifecycle
Adding HTTP metrics exposed via GET /metrics in Prometheus format (latency + status code counters)
Ensuring safe logging practices (no request bodies or sensitive headers)
Optionally enriching /health with runtime metadata (uptime, etc.)

I’ll also include tests/manual verification steps to confirm correlation IDs and metric increments under concurrent requests.

I can deliver a draft PR within 24 hours as required.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @engr-shalom to this issue.

[OsagieCynthia]

@OsagieCynthia has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I will love to work on this issue please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OsagieCynthia to this issue.

[drips-wave]

Congratulations, @OsagieCynthia! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @OsagieCynthia: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊