Add docs for client API layer conventions and how to add a new server call

[Chucks1093]

Summary

The client has an API layer that wraps server calls but its conventions — file location, naming, error handling pattern, and how to add a new endpoint — are undocumented. Contributors adding features that need new server data do not know where to start.

Scope

• Document the API layer folder structure and file naming convention
• Explain how to add a new endpoint call: where the function lives, how errors are handled, and how it connects to a React Query hook
• Include a minimal worked example of a new GET call from API function to hook to component

Acceptance Criteria

• Folder structure and naming convention are documented
• Error handling pattern is explained
• Worked example covers API function, hook, and component usage

ETA: 12 hours

---

Coordinate on Telegram

[ekwe7]

I would love to work on this issue. I have experience building production ready applications and collaborating through GitHub workflows. I'll carefully analyze the current implementation, propose a reliable solution, and submit a well-tested PR. My focus is on clean code, maintainability, and timely delivery

[Gutopro]

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

Can this be assigned to me

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

[zane1502]

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

Hi, I would like to work on this issue

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

[grantfox-oss]

🦊 GrantFox — @zane1502 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #445)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@zane1502's PR #449 was approved and merged by @Chucks1093.

🏆 @zane1502: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (223 total points). Track your full progress on GrantFox.

👏 Great work, @zane1502! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @zane1502 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @zane1502: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.