> For the complete documentation index, see [llms.txt](https://docs.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trybit.com/cms-plugins/list/getcourse.md).

# GetCourse

Below there is a simple instruction on how to integrate CryptoCloud on GetCourse:

1. Sign up on the website <https://app.trybit.com/registration>.
2. Read the instructions in your personal account.
3. Add your project in your personal account by filling in the required boxes. In the CMS list, select GetCourse.

**Your website:**\
<https://domain.com/>

**Successful URL:**\
<https://domain.com/thank-you\\>
(can be any link)

**Unsuccessful URL:**\
<https://domain.com/fail\\>
(can be any link)

**URL for notifications:**\
<https://account\\_name.getcourse.ru/pl/api/deals>

**Getcourse API**\
The key can be found at <https://account\\_name.getcourse.ru/saas/account/api>

4. In the list of pages select «Order Payment» and proceed to edit this page.
5. Go to the GetCourse website: Website — Pages — System pages — Order payment.

<figure><img src="https://app.cryptocloud.plus/img/integrations/instructions/getcourse/1_en.png" alt=""><figcaption></figcaption></figure>

6. Select a place to insert the block and click on the «Add Block» button on the right side of the screen.
7. In the window that opens, select «HTML block».
8. Disable the «WYSIWYG» mode and tick the «Replace variables» checkbox.

<figure><img src="https://app.cryptocloud.plus/img/integrations/instructions/getcourse/2_en.png" alt=""><figcaption></figcaption></figure>

9. Open the inserted HTML block and replace all the content with this code. Before inserting the code, specify SHOP ID, API KEY and CURRENCY (EUR / USD / GBP / UAH / other currency). You can find them in the project settings in your CryptoCloud personal account.

```javascript
<link href="https://api.cryptocloud.plus/static/widget/css/app.css" rel="stylesheet" >
<vue-widget shop_id="YOUR_SHOP_ID" api_key="YOUR_KEY" currency="CURRENCY" ></vue-widget>
<script src="https://api.cryptocloud.plus/static/widget/js/app.js"></script >
```

<figure><img src="https://app.cryptocloud.plus/img/integrations/instructions/getcourse/4_en.png" alt=""><figcaption></figcaption></figure>

10. Click the «Save» button in the upper right corner of the page and go to the page viewer.

<figure><img src="https://app.cryptocloud.plus/img/integrations/instructions/getcourse/5_en.png" alt=""><figcaption></figcaption></figure>

11. The module is ready to work! Before publishing the payment method on the website, you need to [test the integration](https://docs.trybit.com/start/test-integration.md).


---

# 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.trybit.com/cms-plugins/list/getcourse.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.
