Define Streams GraphQL schema

[pragmaticAweds]

Repository

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

Migrated from Fundable-Protocol/stellar_indexer#14.

Context

The streams GraphQL schema should describe the public API shape before Apollo resolvers are implemented.

Scope

• Expand indexer/streams/schema.graphql
• Add types for streams, withdrawals, and cancellations
• Add query input shapes needed for filters/pagination
• Keep schema aligned with the database model

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

Suggested Files or Packages

• indexer/streams/schema.graphql

[Timothy2025-20]

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

Hi maintainer, am a software engineer with years of experience and an enthusiast in open source projects. i will like to resolve this issue if assigned to me, Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Timothy2025-20 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 worked on GraphQL backends where the schema serves as the contract between the database and client applications, designing strongly typed APIs that remain consistent as resolvers and services evolve. I have implemented similar GraphQL schemas with filtering, pagination, and domain-specific types while ensuring alignment with the underlying data model.

To tackle this issue, I would:

• Review the existing indexer data model to ensure the GraphQL schema accurately reflects the underlying database entities.

• Expand indexer/streams/schema.graphql with complete type definitions for streams, withdrawals, and cancellations.

• Define the required query input types for filtering, sorting, and pagination while keeping the schema extensible for future resolvers.

• Ensure relationships between entities are modeled consistently with the database schema and anticipated resolver behavior.

• Update any relevant documentation to reflect the new GraphQL API contract.

• Add or update tests validating the schema and ensuring compatibility with the existing indexer package.

• Verify 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: 6–8 hours.

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

[femiolutayo]

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

Hello Maintainer. I would love to work on this issue. Please assign to me. Thank you

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

[Devdave-0x]

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

i can work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Devdave-0x to this issue.

[Truphile]

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

I've worked on similar GraphQL schema design tasks before, defining API contracts ahead of resolver implementation and keeping schemas aligned with the underlying data model. I'm experienced with pagination/filter input types, schema evolution, and ensuring GraphQL definitions remain type-safe and easy to extend.

For this task, I'll expand the streams schema with the required types and query inputs, keep it consistent with the indexer database model, update any necessary documentation or tests, and verify everything passes the project's type-check, lint, and test pipelines.

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

[modrispath]

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

I'd like to take this on.

I'll expand indexer/streams/schema.graphql with types for Stream, Withdrawal, and Cancellation, keeping the field names and types aligned with the database model from #32. Query input types will cover the filter and pagination shapes needed for listing and filtering streams by the obvious fields (sender, recipient, status, date range).

I'll make sure all the bun run checks pass (type-check, test, lint for both root and indexer) before opening the PR, and keep the changes strictly within the schema file with no resolver or unrelated package work.

Ready to start once #32 is merged.

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

[pre-cious-Igwealor]

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

Hi, my name is Precious Igwealor, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Expand indexer/streams/schema.graphql with well-typed GraphQL types for streams, withdrawals, and cancellations, keeping all field names and data shapes aligned with the existing database model established in Define Streams database schema #32.
2. Define query input types for filtering and pagination across all three entities, covering common filter fields such as status, date ranges, and address lookups with cursor-based or offset pagination support.
3. Add or update relevant tests to validate schema correctness and ensure resolvers can be implemented against the defined types without shape mismatches.
4. Confirm all six lint, type-check, and test commands pass cleanly (bun run type-check, bun run test, bun run lint, bun run indexer:type-check, bun run indexer:test, bun run indexer:lint) with no schema violations or import errors.

ETA: 10 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pre-cious-Igwealor to this issue.

[drips-wave]

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

🧑‍💻 @pre-cious-Igwealor: 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 🌊