Create Apollo GraphQL API package

[pragmaticAweds]

Repository

This issue belongs in Fundable-Protocol/Backend under indexer/.

Migrated from https://github.com/Fundable-Protocol/stellar_indexer/issues/20.

Context

The API should be separated from ingestion and expose indexed stream/distribution data through Apollo Server.

Scope

• Add api workspace package
• Add Apollo Server setup
• Compose schemas from domain packages
• Add resolvers backed by PostgreSQL
• Support basic filters, pagination, and sorting
• Add API tests for basic queries

Out of Scope

• Unrelated package work
• Docker, CI, or deployment work unless named in scope
• Broad refactors outside the touched package

Acceptance Criteria

• Scope items are complete
• Relevant tests are added or updated
• Documentation is updated when needed
• bun run type-check passes
• bun run test passes
• bun run lint passes
• bun run indexer:type-check passes
• bun run indexer:test passes
• bun run indexer:lint passes

Dependencies

• Define Streams database schema #32
• Define Streams GraphQL schema #33
• Define Distributions database schema #36
• Define Distributions GraphQL schema #37

Suggested Files or Packages

• indexer/api/
• indexer/streams/schema.graphql
• indexer/distributions/schema.graphql
• indexer/common/src/db/

[Banx17]

@Banx17 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day Team, I would love to work with you on this issue, please kindly assign thanks.

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

[Franklivania]

@Franklivania has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I am Franklin. I have built GraphQL backends with Apollo Server on top of PostgreSQL-backed services, designing modular schemas, typed resolvers, and reusable data access layers for scalable APIs. I have worked on similar architectures where indexing pipelines, database repositories, and GraphQL packages are kept decoupled while exposing efficient filtering, pagination, and sorting capabilities.

To tackle this issue, I would:

• Create the new indexer/api workspace package and configure it within the existing monorepo.

• Set up Apollo Server with a modular architecture that cleanly separates schema composition, resolvers, and database access.

• Compose the GraphQL schema from the streams and distributions domain packages to maintain a single unified API.

• Implement PostgreSQL-backed resolvers using the existing repository layer in indexer/common/src/db, avoiding direct SQL inside resolvers.

• Add support for filtering, pagination, and sorting across stream and distribution queries while keeping resolver performance in mind.

• Write API tests covering basic queries, filtering, pagination, and resolver correctness.

• Update documentation describing the API package structure, schema composition, and development workflow.

• Validate the implementation by running:

  • bun run type-check
  • bun run test
  • bun run lint
  • bun run indexer:type-check
  • bun run indexer:test
  • bun run indexer:lint

ETA: 10–12 hours.

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

[drips-wave]

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

🧑‍💻 @Franklivania: 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 🌊