SMS · API · GATEWAY · DE
SMS API GATEWAY · 01

Your SMS API.
Direct. Reliable. Across Germany.

A REST API for business SMS delivery within Germany. Pay per use or choose a flat rate — we tailor the plan to your volume.

GermanyNationalIntegrationRESTREST-APIWebhooksDelivery-ReportsAPI AccessUnicodeSMS GermanyNationalIntegrationRESTREST-APIWebhooksDelivery-ReportsAPI AccessUnicodeSMS GermanyNationalIntegrationRESTREST-APIWebhooksDelivery-ReportsAPI AccessUnicodeSMS
Features · 02

What the API does — and
what it leaves out.

No bloated feature list. Just what matters in production: nationwide delivery, traceable sending, clear reports and an endpoint that works.

F.01

Nationwide delivery to all German mobile networks.

Send SMS messages to German mobile networks. Delivery times depend on the destination network and whether the recipient's device is reachable.

+49
F.02

Servers in Germany.

Infrastructure hosted entirely in German data centres. No data flows outside the EU.

DE · RZ
F.03

REST-API.

One POST endpoint, a JSON payload and a bearer token. Integrate in under an hour.

POST /v1/sms
F.04

Delivery reports via webhook.

Real-time status updates sent back to your endpoint.

→ webhook
F.05

Unicode & 160 characters.

Standard GSM or UTF-8. Long messages are concatenated automatically.

UTF-8
F.06

Configurable sender ID.

Alphanumeric sender ID or short code, in line with German Federal Network Agency requirements.

FROM=...
Integration · 03

One endpoint.
One request.

If you've worked with bloated SMS platforms, you'll appreciate the difference. With us: one token, one POST, one response.

  • HTTPS / TLS 1.3
  • Bearer-Token-Auth
  • JSON Request & Response
  • Idempotency keys to prevent duplicate sends
  • Rate-Limit-Header (X-RateLimit-*)
  • Full OpenAPI specification on request
Terminal · curl
# Send an SMS
curl -X POST https://api.acw.gmbh/v1/sms \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "to":      "+49170XXXXXXX",
    "from":    "ACW",
    "text":    "Your code is 482931.",
    "webhook": "https://api.kunde.de/sms-status"
  }'

# Response
{
  "id":       "msg_8f3a...",
  "status":   "queued",
  "to":       "+49170XXXXXXX",
  "created":  "2026-05-20T09:00:00Z"
}
Use Cases · 04

Why our clients
send SMS.

Three scenarios we handle every day. Have a different use case? Give us a call and we'll take a look.

U.01

Transactional SMS

Security-sensitive and delivery-critical messages, where late or lost delivery is not an option. Routing is prioritised accordingly.

2FA · OTP · Login-Codes · Order-Confirmation
U.02

Notifications

Reminders and status updates that email fails to get across. Low per-message costs and predictable volumes.

Appointments · Delivery Status · System Alerts · Reminders
U.03

Campaigns

Marketing messages with opt-in management and unsubscribe handling. We help configure your setup in line with German Federal Network Agency requirements.

Promotions · Newsletters · Re-engagement · Opt-in
Plans · 05

Two pricing models.
One that fits.

Pricing depends on volume, routing and service level. Let's talk — we usually have a quote ready within 24 hours.

Plan A

Pay per Usage

Pay for each SMS sent. No minimum volume or base fee. Ideal for irregular or growing volumes.

  • Only pay for messages sent
  • Volume discounts above an agreed threshold
  • No lock-in, cancel monthly
  • Ideal for 1,000–100,000 SMS per month
Pricing on request
Enquire about pay-per-use →
Plan B

Flatrate

A fixed monthly fee for an agreed allowance. Predictable costs for budget-conscious teams or consistent sending volumes.

  • Fixed monthly allowance included
  • Predictable costs, no unexpected spikes
  • Lower per-message costs than pay-per-use
  • Ideal from around 10,000 SMS per month
Pricing on request
Enquire about flat-rate plans →
COMPLIANCE
Legal & Security · 06

Compliance is not
a marketing feature.

Privacy and security belong in project planning. The agreed configuration, service providers and contractual terms determine the requirements.

Server Location

Hosting locations, data flows and service providers must be assessed against your requirements before deployment.

Privacy

Processing data on your behalf requires an agreement under Article 28 GDPR. Legal bases and deletion periods must be defined for each use case.

Lawful Messaging

Marketing SMS generally requires prior explicit consent unless a statutory exception applies. The sender is responsible for ensuring that messages are sent lawfully.

Encryption

Encryption and access-control requirements are defined in the technical scope of service.

Service Providers

The service providers involved in delivery must be reviewed for the specific scope of service.

Monitoring

Monitoring, support hours and service levels are governed by the agreement.