GatewayAPI · Danish SMS
GatewayAPI integration: a Danish SMS gateway
GatewayAPI integration means your system sends SMS through a Danish gateway API and logs delivery status on the case or the user. GatewayAPI (OnlineCity) is one of the sockets Danish developers actually have in hand. For pure DK SMS at volume it often beats the global platforms on price. “Your code is 482191” is a transaction. “We have an offer this week” is marketing: consent and opt-out. Do not mix them in the same sender and the same template box. Two-way is possible with an inbound number — then you must parse replies and bind them to a case. [Twilio](/articles/integrations/twilio-integration) wins when voice and global numbers are the product.
8 min read · Updated 28 August 2026
If you only need Danish SMS this year, start here — not at MessageBird, unless you already have a Bird account. Automation that triggers the message.
Transaction vs marketing
Transaction
- Code, booking, “technician is on the way”
- Log on the case. No offer copy
- Idempotency so retry does not spam
Marketing
- Consent as master in one place
- Opt-out that works
- A different sender or template box
Out
Your system sends with your case id as reference.
In
Inbound number. Parse YES/NO or free text.
Bind
The reply lands on the case. Unknown sender becomes a queue, not a hole.
What to do now
Count Danish SMS per month and say whether you need replies in. That is the price and the design. Send the numbers.
FAQ about GatewayAPI integration
Can we get two-way?
Is GatewayAPI cheaper than Twilio in DK?
May transaction and marketing share a sender?
Who is OnlineCity?
Want us to build it for you?
You get a fixed-price proposal within 24 hours.
