> For the complete documentation index, see [llms.txt](https://docs.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsvblockchain.org/network-topology/spv-wallet/components/web-app-and-api.md).

# Web App & API

Example application

## Example Application integrated with SPV Wallet

The frontend web wallet application allows users to register, make transactions, and see their balance. This is what we'd expect you to replace with your own application front end, but is included in the deployment to provide a working demo for basic payment functionality.

<figure><img src="https://2147185133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWtK4ab0ntyPZBmGoKq4t%2Fuploads%2Fgit-blob-eca378b0aec6143581138dd5d80a61d4c8c360c2%2FWeb%20App%20SPV%20Wallet.png?alt=media" alt=""><figcaption><p>SPV Wallet - Web App</p></figcaption></figure>

### Front End

{% embed url="<https://github.com/bitcoin-sv/spv-wallet-web-frontend>" %}

### Back End

The backend API is coupled with the web wallet, and demonstrates use of the Wallet Client library.

{% embed url="<https://github.com/bitcoin-sv/spv-wallet-web-backend>" %}

## Clients

The client libraries themselves are available separately such that integrating with your own front end should be straightforward.

### Golang

{% embed url="<https://github.com/bitcoin-sv/spv-wallet-go-client>" %}

### JavaScript

{% embed url="<https://github.com/bitcoin-sv/spv-wallet-js-client>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsvblockchain.org/network-topology/spv-wallet/components/web-app-and-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.