> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/ja/nitsuitebitaidesuka/getting-started/readme-1/im-a-partner/step-2-apply-to-brands.md).

# ステップ2：ブランドに応募しましょう！

ブランドとのパートナーシップを始める方法は2つあります。方法は以下のとおりです：

* [ブランドに提案を送る](/partner/ja/nitsuitebitaidesuka/platform-features/working-with-brands/applying-to-brands/find-and-apply-to-brands.md) 一緒に仕事をしたい
* [提案を受け入れる](/partner/ja/nitsuitebitaidesuka/platform-features/working-with-brands/applying-to-brands/manage-your-brand-invitations-and-applications.md) ブランドから送られてきた

## 応募後

1. ブランドにあなたの応募が届きます。報酬、タスク、その他の詳細について交渉する場合があります。
2. 応募が承認または却下されると、メールとアプリ内通知が届きます。
3. 確定した [契約書](/partner/ja/nitsuitebitaidesuka/platform-features/working-with-brands/contracts/contracts-explained-for-partners.md) には、ブランドの報酬の詳細と要件が表示されます。
4. リンクやプロモコードを作成・共有して、収益を始めましょう！

<div data-with-frame="true"><figure><img src="https://3659882269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-439591c1ea49d95d3f19ccf5fe9da32add3ab710%2Ffd3a73c05de3aee022c65ec836a172889aac6c4cd105fbb5e6eae908cee8e7b1.svg?alt=media" alt=""><figcaption></figcaption></figure></div>


---

# 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://help.impact.com/partner/ja/nitsuitebitaidesuka/getting-started/readme-1/im-a-partner/step-2-apply-to-brands.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.