---
title: "Deploy Secured Signal Rest API"
description: "Template for a secure Signal Rest API"
category: "Bots"
url: https://railway.com/deploy/secured-signal-rest-api
---

# Deploy Secured Signal Rest API

Template for a secure Signal Rest API

**[Deploy Secured Signal Rest API on Railway](https://railway.com/template/secured-signal-rest-api)**

- **Creator:** Hunter Bertoson's Projects
- **Category:** Bots
- **Total deploys:** 19

## Template content

### secured-signal https://signal.org/assets/images/favicon/favicon.svg

- **Image:** ghcr.io/codeshelldev/secured-signal-api:latest
- **Public domain:** Yes

### signal-api https://signal.org/assets/images/favicon/favicon.svg

- **Image:** bbernhard/signal-cli-rest-api:latest
- **Health check:** /v1/health

## Documentation

# Deploy and Host Secured Signal Rest API on Railway

Secured Signal Rest API is a lightweight authentication proxy for signal-cli-rest-api. It adds bearer token authentication to protect your Signal messaging API, allowing you to safely expose Signal messaging capabilities to your applications without exposing the underlying API directly.

## About Hosting Secured Signal Rest API

Hosting Secured Signal Rest API requires deploying two services: the signal-cli-rest-api backend (which handles actual Signal protocol communication) and the secured-signal proxy (which adds authentication). The signal-cli-rest-api service needs persistent storage to maintain your Signal account registration and encryption keys. The proxy sits in front, validating bearer tokens before forwarding requests to the backend. Railway's internal networking allows the backend to remain private while only the authenticated proxy is publicly accessible.

## Common Use Cases

- Adding Signal notifications to web applications or services
- Building chatbots or automated responders on Signal
- Integrating Signal messaging into business workflows (alerts, OTP delivery, customer communication)

## Dependencies for Secured Signal Rest API Hosting

- signal-cli-rest-api (backend Signal messaging service)
- Persistent volume for Signal account data and encryption keys

### Deployment Dependencies

- [signal-cli-rest-api](https://github.com/bbernhard/signal-cli-rest-api) - The underlying Signal messaging API
- [secured-signal-api](https://github.com/CodeShellDev/secured-signal-api) - Authentication proxy

### Implementation Details

Configure the secured-signal service with these environment variables:
```
API__URL=http://signal-api.railway.internal:8080
API__TOKENS=[your-token-1, your-token-2]
```

Keep the signal-cli-rest-api service private (no public domain) and only expose the secured-signal proxy publicly. Requests require a bearer token in the Authorization header.

## Why Deploy Secured Signal Rest API on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Secured Signal Rest API on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

## Similar templates

- [Telegram JavaScript Bot](https://railway.com/deploy/5lRkWa) — A template for Telegram bot in JavaScript using grammY
- [Cobalt Tools [Updated Aug ’26]](https://railway.com/deploy/cobalt) — Cobalt Tools [Aug ’26] (Media Downloader, Converter & Automation) Self Host
- [Telegram Gateway](https://railway.com/deploy/railway-telegram-gateway) — Multi-bot Telegram webhook gateway with WebSocket event streaming

Open this page in a browser: https://railway.com/deploy/secured-signal-rest-api