> For the complete documentation index, see [llms.txt](https://docs.sparkloop.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sparkloop.app/client-api/early-access.md).

# Early Access

The Client API is in early beta and only enabled on request. Read this page before you start building: it explains who the Client API is for, what to expect as a beta partner and how to apply.

### Do you need the Client API?

Most publications don't. The [Signup Flow](https://www.tella.tv/video/vid_cmqjp1z7j00nt0bj66dks4rqi/view) already shows recommendations, surveys and offers to new subscribers right after they sign up, with no code beyond the SparkLoop script. It's also customizable:

* Want to open it yourself after your own signup or survey step? Use [manual tracking](https://help.sparkloop.app/en/articles/5867950-manually-track-subscribers).
* Want to decide where and when it shows? Use [visibility rules](https://help.sparkloop.app/en/articles/6824529-visibility-rules).

Reach for the Client API when you need to render recommendations and offers in your own UI, with your own markup and flow.

### What to expect from the beta

The Client API lets you build SparkLoop recommendations and offers directly into your own website and signup flow. It's currently in early beta, so before you start, here's what you need to know as a beta partner:

* **It's a beta, so expect change.** The API will evolve over the coming weeks. We'll give you advance notice of any breaking changes, but we'll need you to update your integration within 24 hours of a change going out. If an integration can't be kept current, we may need to pause it until it is.
* **You own your integration.** Building, testing, monitoring and maintaining it is up to you and your team. If an integration breaks or starts sending problematic traffic into the network, we'll pause it until it's fixed. SparkLoop won't compensate you for any lost earnings.
* **Subscriber consent has to be genuine.** Readers must knowingly choose to subscribe or claim an offer, with no misleading copy or dark patterns.
* **This is the path forward.** Sending referrals through the REST API is being deprecated, so if you're currently integrating that way, you'll need to migrate to the Client API regardless.

### How to apply

Fill in the [early access form](https://forms.reform.app/sparkloop/client-api-early-access). We'll ask you for:

* Your publication.
* What you're building and why the Signup Flow isn't a fit.
* Every domain your integration will run on, including staging and test domains. A domain covers all of its subdomains, and calls from any domain not on your list are rejected.

### After approval

1. **Build and test in draft first.** We enable a draft integration on your domains so you can start building. Run every call in [test mode](/client-api/testing-your-integration.md) while you do.
2. **Record a demo.** When you're done, record a short screen recording of your flow in action, or share a URL where we can try it along with the steps to follow.
3. **We review before you go live.** Share your demo with us. We review the integration and activate it so you can make real referrals on your live website.

Next: [Getting Started](/client-api/getting-started.md).