# Manage account and integration settings

> Update profile details and time zone, configure postbacks and webhooks, manage API keys, and find the technical documentation.
> Source: https://docs.23telecom.co.uk/guide/settings/

Instructions for LLMs: This is one page of the 23 Telecom messaging API docs
(SMS today; more channels planned). Base URL: https://restlink23telecom.com/api/v1,
auth via the X-API-Key header. Match errors on the error_code field, never on
description text. Full docs: https://docs.23telecom.co.uk/llms-full.txt · Schemas: https://docs.23telecom.co.uk/openapi.yaml

Account pages hold personal settings. Integration pages control data sent to external systems.

## Update the profile and time zone

1. Expand **Settings** in the portal menu.
2. Open **Account**.
3. Complete **Email**, **Phone**, and **Company**. All three fields are required.
4. Select **Save Changes**.
5. Find **Account Time Zone**.
6. Choose **Time Zone**.
7. Select **Save Time Zone**.

The account time zone is used for reports, dashboard dates, filters, and displayed times. A scheduled broadcast uses the time zone selected in its own schedule. Editing these account fields requires permission to update settings.

## Set a postback URL

1. Expand **Settings** in the portal menu.
2. Open **Integrations**.
3. Find **Webhook Settings**.
4. Enter **Postback URL**.
5. Select **Save Webhook Settings**.

The URL must be a public address beginning with `http://` or `https://`. Private and internal addresses are rejected. Developers should read [tracker postbacks](https://docs.23telecom.co.uk/webhooks/postbacks/) before processing these requests.

## Configure webhooks

1. Expand **Settings** in the portal menu.
2. Open **Webhooks**.
3. Stay on **Settings**.
4. Enter the destination and choose payload fields for each event card.
5. Select **Test** on a configured card.
6. Select **Save Settings** in the page header.
7. Open **Logs** to review recent attempts.

Read the developer documentation in the [webhook overview](https://docs.23telecom.co.uk/webhooks/overview/) for payload details. Testing and saving require webhook-update permission.

## Create an API key

1. Expand **Settings** in the portal menu.
2. Open **API Keys**.
3. Select **Create API Key**.
4. Enter **Key Name**.
5. Choose **Key preset**. Use the integration preset only for its named integration.
6. Choose **Permissions** for a standard key.
7. Turn on **Require request signature (HMAC-SHA256)** when your integration signs requests.
8. Turn on **Test mode (sandbox)** when you need simulated sends.
9. Select **Create Key**.
10. Copy the key and any secret immediately.

The full credential is shown only once. Follow the developer [API keys and permissions guide](https://docs.23telecom.co.uk/api-keys/) for authentication and signatures.

## Troubleshooting

1. Check the scheme when a postback or webhook URL is rejected.
2. Use a public destination because private or internal addresses are rejected.
3. Open **Logs** to inspect a failed webhook attempt.
4. Ask the account owner to review settings, webhook, or API-key permissions when an action is disabled.