> For the complete documentation index, see [llms.txt](https://investec.gitbook.io/programmable-banking-community-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events.md). # Build challenges & hackathons The Investec Developer community hosts build challenges and hackathons throughout the year, centered around the Investec banking API and programmable card. If you are new to the community, this is a great way to learn more about how to apply API banking to innovative solutions and to meet others in the community. To chat with other community members about the things you have been building - whether to show off your build or get advice - join the [#02\_buildspace channel ](https://investec-dev-com.slack.com/archives/C05MFMYUPE2)on the Investec Developer Slack. ### Open challenges * [Investec Dev Quest](https://github.com/Investec-Developer-Community/investec-dev-quest) | A local-first, CLI-level-based developer coding game ### Past events and challenges #### 2026 * [Q2 2026 Bounty Challenge | API Side Hustle](/programmable-banking-community-wiki/get-building/build-events/q2-2026-bounty-challenge-or-api-side-hustle.md) * [Q3 2026 Bounty Challenge | Future You](/programmable-banking-community-wiki/get-building/build-events/q3-2026-bounty-challenge-or-future-you.md) #### 2025 * [Q1 2025 Bounty Challenge ](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q1-2025-bounty-challenge-or-path-to-financial-health)| Path to Financial Health * [Q2 2025 Bounty Challenge | Every‑Day Money Hack](/programmable-banking-community-wiki/get-building/build-events/q2-2025-bounty-challenge-or-every-day-money-hack.md) * [Q3 2025 Bounty Challenge | Smart & Secure Banking](/programmable-banking-community-wiki/get-building/build-events/q3-2025-bounty-challenge-or-smart-and-secure-banking.md) * [Q4 2025 Bounty Challenge | History Repeats Itself](/programmable-banking-community-wiki/get-building/build-events/q4-2025-bounty-challenge-or-history-repeats-itself.md) #### 2024 * Q4 2024 Investec & Microsoft Hackathon * Q3 2024 Investec & DVT Hack day * [Q4 2024 Bounty challenge ](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q4-2024-bounty-challenge-festive-api-wrappers)| Festive API wrappers * [Q3 2024 Bounty challenge ](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q3-2024-bounty-challenge-every-day-solutions)| Everyday solutions * [Q2 2024 Bounty challenge](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q2-2024-bounty-challenge-or-card-code-snippets) | Card code snippets * [Q1 2024 Bounty challenge](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/closed-q1-2024-bounty-challenge-or-the-tutorial-quest) | The tutorial quest #### 2023 * Q4 2023 | Investec & Agile Bridge Hack day * [Q4 2023 Bounty challenge](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/open-bounties-playground-or-banking.make.dev) | Banking API tools * [Q2 2023 Bounty challenge](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/open-q2-2023-bounty-challenge) | Code snippets * [Q1 2023 Bounty sprint challenges](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/closed-q1-2023-bounty-challenge) | Three themed challenges over two weekends each. #### 2022 * [Q4 2022 EskomSePush hackathon ](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/closed-eskomsepush-build-challenge/eskomsepush-build-challenge-submissions)| Eskom API building⚡ * [Q2 2022 Investec & OfferZen Hackathon](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q2-2022-hackathon-or-low-code-no-code/2022-hackathon-or-low-code-no-code-or-submissions) | Low-code/ no-code Spreadsheet Banking * [Q1 2022 Bounty challenges](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/closed-spreadsheet-banking-or-bounties) | Spreadsheet Banking #### 2021 * [Q4 2021 Investec & OfferZen Hackathon](https://docs.google.com/spreadsheets/d/1cWZQtru2zXkkVjEnbOZiCbwbTW1LcpgEsUalt1Vwlog/edit?usp=sharing) | Transfer APIs * [Q2 2021 Investec & OfferZen Hackathon](https://docs.google.com/spreadsheets/d/1Rh7bjikdBxGVXoCIKS8XU3apjvCwUIxagt1Nziuz_u0/edit?usp=sharing) | Programmable Banking **2020** * [Q4 2020 Investec & OfferZen Hackathon](https://drive.google.com/file/d/1j3xv81VSj563uhcfbF-0Ms8bINguhvYb/view) | Programmable Banking --- # 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://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events.md?ask=&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.