> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/resources-ja/porishtosekyuriti/porishtosekyuritikonpuraiansu/reberu-1/bakkuapputokaibu/flosum-bakkuapputokaibunosekyuritioyobikonpuraiansu/api.md).

# API

ユーザー資格情報は、ハッシュ（ソルト）SHA-256アルゴリズムを使用して保存されるか、可逆のAES-256以上が使用されます。バルクおよびREST APIの制限は、顧客の要件に合わせて定義できます。SSO（認証および認可の両方）にはOpenID Connect経由のOAuth 2.0が使用され、OpenIDおよび関連標準をサポートします。\
\
アプリは、利用可能なSalesforce API制限のうち1日あたりの割合としてAPI使用量を制限します。バックアップログには制限に達したことが表示され、自動的にスロットルされてSalesforceのパフォーマンスに影響が出ないようにします。


---

# 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.flosum.com/resources/resources-ja/porishtosekyuriti/porishtosekyuritikonpuraiansu/reberu-1/bakkuapputokaibu/flosum-bakkuapputokaibunosekyuritioyobikonpuraiansu/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.