> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/developer-docs/api-samples/importing-public-status-page-subscribers.md).

# Importing Public Status Page Subscribers

By default public status page subscribers need to confirm their subscription in the channel that they have subscribed too - a confirmation notification is send at creation.

When moving from other providers to ilert, you might want to migrate your existing subscribers that have already opted-in to their channels - without bothering your customers / subscribers with a resubscription.

### You may use the public status page subscription bulk API for this operation:

Send a **POST** request to

```
https://api.ilert.com/api/status-pages/{status-page-id}/subscribers_bulk?import=true
```

```json
[
    {
        "target": "+49171123123", // EMAIL, PHONE NUMBER, URL
        "type": "SMS" // EMAIL, SMS, WEBHOOK
        "locale": "en-GB", // en-GB | de-DE
        "services": [1, 2, 3] // optional list of service (id) restrictions (just leave out the whole key if not needed)
    },
    ...
]
```

{% hint style="danger" %}
Do not forget the **import=true** query parameter, otherwise you will send out confirmation notifications to your subscribers! We recommend testing with your own sample targets first, before bulking through thousands of subscribers. We suggest sending a maximum of 100-250 subscribers per HTTP call.
{% endhint %}

Visit the web UI (Status page -> Subscribers tab) to confirm your import.

{% hint style="warning" %}
Note that removing a confirmed subscriber will send an unsubscription notification to the target.
{% endhint %}


---

# 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.ilert.com/developer-docs/api-samples/importing-public-status-page-subscribers.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.
