# SSTI_SERV_EVENT_INITIALIZED (SSTI API Event)

Event fires when SSTI receives the new configuration from server (for example, on group name change).

## Variables

The following table shows input values (you send them with the API call) and returned output values.

| Variable |     | Required | Description |
|----------|-----|----------|-------------|
| *link_message* parameters: |     |          |             |
|          | num |          | SSTI_EVENT_INITIALIZED |
|          | str |          | \-- not used -- |
|          | id  |          | \-- not used -- |

## Comments

This event fires when SSTI server successfully reads the configuration notecard, and all internal structures are initialized.

The server initialization events order is the following:


1. *Server restarted*
2. [SSTI_SERV_EVENT_RESET](/doc/5abf00a4-c1e8-4cef-b441-30f0a531216b)
3. *Server starts reading config, this takes 10-20 seconds*
4. *Config notecard has been read, config is known now*
5. **SSTI_SERV_EVENT_INITIALIZED**
6. [SSTI_SERV_EVENT_GROUP](/doc/ab39cbd9-28b1-4a88-8953-33cfa44d8205) (sent without your request)
7. [SSTI_SERV_EVENT_CLOUD](/doc/a5b831dd-134a-4960-bc3d-fcdfa06246c5) (sent without your request)
8. *SSTI server starts doing its work*

**Important:** The server can be restarted by the user or sim at any moment. Be prepared to get this event at any time (for example, customer may edit the configuration notecard).

## Example

This example demonstrates the arrival of SSTI initialization events


:::warning
Code sample missing: the old wiki failed to render this code block, so it was not in the source. Restore it from the original source.

:::


:::warning
Code sample missing: the old wiki failed to render this code block, so it was not in the source. Restore it from the original source.

:::