> For the complete documentation index, see [llms.txt](https://docs.sfox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sfox.com/connect/introduction/resources/integration-options.md).

# Integration Options

Connect offers two options for streamlines flows.

## API (backend flow)

Automate all interactions with sFOX using the sFOX Connect API

{% content-ref url="/pages/uNE3QRhQ3rD6U6LaDQOV" %}
[REST API](/connect/rest-api/rest-endpoints.md)
{% endcontent-ref %}

{% content-ref url="/pages/X2NwSb3SpynHCChfDWeJ" %}
[WebSocket API](/connect/websocket-api/websocket-feeds.md)
{% endcontent-ref %}

## SSO (hybrid flow)

{% hint style="info" %}
SSO integrations are best used by partners aiming to utilize sFOX's front end.&#x20;

**However, please note that currently, the sFOX front end does not support co-branding.**
{% endhint %}

Embed an sFOX Connect iframe into your application and authenticate your users through IdP initiated SSO. Learn more about SSO integrations:

{% content-ref url="/pages/QIm8caaym7W6MQ1afBfj" %}
[Single Sign-On](/connect/single-sign-on/overview.md)
{% endcontent-ref %}


---

# 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.sfox.com/connect/introduction/resources/integration-options.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.
