Best Voice API for Outbound Calls in Germany 2026

Quick answer: For an AI agent that phones German leads, Zian is our pick. On raw voice APIs, rates read 12 November 2026 put 3,000 answered calls (5,000 minutes, 70% to mobiles, German or EEA caller ID) at $153.80 on Telnyx with its own German number ($113.00 with another EEA country’s number), $175.08 on Plivo (inside a $1,000 monthly minimum), $230.04 on Twilio and $371.40 on Vonage. sipgate’s Flow starts at €249.95, with no separate speech charge listed.

Choosing the best voice calling API for outbound calls in Germany comes down to four things: whether you can get a German (+49) number, which caller ID your calls present, what a minute to a German mobile costs with that caller ID, and where the call data is processed. This page compares five providers on all four: Twilio, Telnyx, Vonage (the Vonage API platform), Plivo and sipgate, the Düsseldorf-based telephony provider whose Flow API is built for voice bots. It uses the German rules behind them: the Bundesnetzagentur’s allocation order for geographic numbers (Verfügung 25/2006), caller-number display under §120 of the Telekommunikationsgesetz (TKG), and the origin-based pricing that European mobile networks apply. Every price comes from the provider’s own price page, price file, pricing API or help centre, read on 12 November 2026.

Where Zian fits for outbound calls to Germany

Zian is our pick when what you need is an agent that phones German leads, holds the conversation in German and books the meeting, rather than a voice API to build that agent from. It is not a CPaaS or a phone system itself; the five APIs on this page are what a team assembles an agent from when it builds its own.

Zian’s agents make outbound calls and follow up by SMS, email and WhatsApp, answer inbound calls 24/7 as an AI receptionist, handle answering machines and voicemail, and book appointments from both directions. zian.ai lists German among its 30+ languages, and it supports voice cloning and CRM integrations with HubSpot, Salesforce, HighLevel and Zapier. SmartReach AI™ sets message, channel and timing by country, and PrecisionPitch AI™ split-tests scripts. Zian has been running outbound acquisition since 2017 and reports 64,521+ qualified sales appointments set. It is in a partnership-application beta with no published prices; each of its three listed plans, including Intel + Widgets (Free Forever), starts with a partnership application. For a done-for-you route, LeadsNow.ai runs on Zian as a managed AI appointment-setting service, is paid per result, reports 50,769+ appointments and answers leads in under 60 seconds, 24/7.

Whichever route you choose, a sales call to a German consumer needs prior express consent; the rules for business calls and AI callers are in our guide to whether AI cold calling is legal in Germany under the UWG.

Best voice calling API for outbound calls in Germany: the comparison

How we filled this table. A cell is filled only from a figure or sentence on the provider’s own pricing page, price file, pricing API, help centre or developer docs, read on 12 November 2026. Outbound rates are for the programmable voice API path an AI agent uses: Twilio Programmable Voice, the Telnyx Voice API (its SIP outbound rate plus a $0.002 Voice API fee), the Vonage Voice API, the Plivo Voice API and the sipgate Flow API. Media streaming, speech recognition, text-to-speech and model charges are excluded, except at sipgate, whose Flow API handles speech-to-text and text-to-speech and lists no separate charge for them. “German or EEA caller ID” means the provider’s own domestic or “from EEA” rate row. Prices are US dollars except sipgate (euros; its Flow prices exclude VAT). The US (+1) column assumes a mainland US number: Telnyx charges its High Surcharge rate to a few +1 area codes, including Alaska (+1 907) and Hawaii (+1 808). Zian and LeadsNow.ai are described only from their own published facts. Disclosure: zian.ai publishes this comparison and Zian appears in it.

Provider	German numbers offered (monthly)	German address needed?	Outbound to a German landline	Outbound to a German mobile: German or EEA caller ID / US (+1) caller ID	Billing increment	EU region option
1. Zian (AI-agent platform pick)	Not a CPaaS: an AI sales and reception agent platform that calls, follows up and books in 30+ languages, German included. No published prices (partnership-application beta).					Private model deployment on customer infrastructure is listed
2. LeadsNow.ai (done-for-you pick)	Managed AI appointment setting that runs on Zian, paid per result.
Twilio	Local $1.35; mobile $30.00 (mobile is domestic-voice-only); toll-free 0800 only after you obtain it from the Bundesnetzagentur	Yes. Local: within the area of the number’s prefix. Mobile: within Germany. Not available to individuals	$0.0283/min, whatever the caller ID	$0.0420 / $0.3763 per min	Partial minutes rounded up to the next full minute	Ireland (IE1) region for Programmable Voice, with listed unsupported features; Frankfurt edge
Telnyx	Local $1 (+$1 one-time); national $1 (+$1); mobile $0.75 (+$1); toll-free $30 (+$40); shared-cost $50 (+$50)	Yes. Local: address matching the area code, utility bill under 3 months old; end users “must be physically present in the country”	$0.0120/min with a Telnyx German number, $0.0101 with another EEA country’s number; $0.0251 with US +1 (all including the $0.002 fee)	$0.0310 with a Telnyx German number ($0.0221 with another EEA country’s number) / $0.0421 per min (including the $0.002 fee)	60/60	api.telnyx.eu processed in Frankfurt; Frankfurt, London or Amsterdam AnchorSite; Data Locality setting “Germany”
Vonage	Landline, on request, 1–3 business days, $1.22 (+$1.22 initial); its price sheet also prices toll-free at $7.27	Yes: proof of local address; proof of need above three numbers	$0.01173/min (domestic, EU or US/CA caller ID); $0.07222 for its catch-all international origin group; $2.79287 from “Remote Countries” or with no caller ID	$0.10039 / $0.10039 per min (EU and US/CA share a row)	Per second	api-eu-4 (Frankfurt) or api-eu-3 (Dublin)
Plivo	None listed for Germany	Not applicable	$0.0135/min from EEA; $1.0674 otherwise	$0.0359 (major networks) or $0.0495 / $0.3850 per min	Voice API 60/60	Data regions documented: US and India; Frankfurt media servers listed
sipgate (Flow API)	German local numbers from your own area code; 3 numbers €4.95 a month on its phone-system price list	Yes: “a fixed address in Germany” you must verify	Flow minute, no landline or mobile split on the Flow page: €249.95 for 2,500 minutes then 9.9 ct, down to 6.9 ct on the €3,499.95 package; speech-to-text and text-to-speech handled by the API, no separate charge listed		“Minutengenaue Abrechnung” (billed by the minute)	Data centres in Frankfurt and Düsseldorf; Flow is EU-hosted

Three caveats change how to read the table. First, Telnyx’s rate data for Germany carries both a “Local” row and a “From EEA” row, and its rate-deck article says which applies: local origination is a call to a country from a number of that country “that was purchased on the Telnyx platform”, while EEA origination uses “a phone number of another country within the EEA”. A Telnyx German number therefore pays the Local row ($0.0310 a mobile minute with the fee); the lower From EEA row ($0.0221) needs a number from another EEA country, and Telnyx’s EEA origin list does not include +44 (UK). Second, Telnyx and Twilio each price a few mobile ranges differently: Telnyx charges Telefónica mobiles $0.0251 from the EEA and $0.0462 on its default row, and a range it labels “Mobile Other” $0.1694 on its Local row, each plus the fee, and Twilio charges $0.3763 to three prefix groups (+491570, +49700, +49701) whatever the caller ID. Third, Plivo’s Germany calling sits outside its pay-as-you-go plan, which “covers the United States and India”; its Enterprise plan “Requires a $1,000/month minimum commit”. Plivo also lists no German numbers, so its from-EEA rates assume a European caller ID your account can present; confirm with Plivo which of its numbers qualify.

The quotable line: on Twilio and Plivo, a minute to a German mobile costs roughly eight to eleven times as much when the call shows a US number instead of a European one.

Why the caller ID decides what a German mobile call costs

European mobile networks charge more to terminate calls that come from outside Europe, and the providers pass that on. Twilio’s help article on origin-based pricing puts it plainly: “Origin is determined by the caller ID of the call”, and “generally calls from outside Europe into Europe will be more expensive than calls within Europe.” Twilio’s EEA list includes Germany, Ireland and the United Kingdom. It also warns that a caller ID “not in the international E.164 format” is likely to be priced as if it came from the US or Canada.

The effect on a German mobile minute differs by provider:

• Twilio: $0.0420 with an EEA caller ID, $0.3763 without one. That is about nine times as much.
• Plivo: $0.0359 to the major networks (Vodafone, T-Mobile, Telefónica, E-Plus) from the EEA, $0.0495 to other mobile networks from the EEA, and $0.3850 otherwise. Plivo’s landline rate moves even further, from $0.0135 to $1.0674.
• Telnyx: $0.0201 from the EEA, $0.029 on its “Local” row and $0.0401 by default, each plus the $0.002 fee. A separate “High Surcharge” row charges $0.5375 when the caller ID starts with one of a list of country codes that includes +61 (Australia), +41 (Switzerland) and +7.
• Vonage: $0.10039 for domestic callers and for its “EU & US/CA” origin group alike, $0.14431 from its catch-all origin group, and $0.66871 both from its “Remote Countries” origin group and for calls with no caller ID (“Non-CLI”).

Telnyx adds a technical condition: calls “terminating into the EEA internationally must include a valid P-Asserted-Identity (PAI) header containing a real, dialable CLI”. If the header is missing, anonymous or invalid, “the call may be rejected or subject to surcharges from the terminating carrier which will be passed onto the customer.”

That is the reason for our decision rule. The +49 Origin Rule: choose a provider by the caller ID it lets you lawfully present from inside the German network, then by its rate for that caller ID, never by its headline rate. For an Australian team that dials Germany on its own +61 number, the rule is the whole decision: Telnyx’s High Surcharge row is roughly 27 times its from-EEA mobile rate, before the $0.002 fee.

What a month of German outbound calling costs on each API

This is the worked bill behind the quick answer; substitute your own inputs. You place 3,000 answered calls a month from two German local numbers, presenting one of them as caller ID. Calls average 1 minute 40 seconds, which is 5,000 minutes of talk. Seventy per cent of the calls (2,100) go to mobiles and 900 to landlines. Each provider’s billing increment is applied per call: at 60-second rounding, a 100-second call is billed as 2 minutes, so 3,000 calls become 6,000 billed minutes; billed per second, they stay at 5,000.

Provider and rate row	Mobile minutes	Landline minutes	Two numbers	Monthly total
Telnyx, “From EEA” row (needs another EEA country’s number, not this scenario’s German numbers), 60/60	4,200 × $0.0221 = $92.82	1,800 × $0.0101 = $18.18	$2.00 (+$2 one-time)	$113.00
Telnyx, “Local” row (its own German number, as in this scenario), 60/60	4,200 × $0.0310 = $130.20	1,800 × $0.0120 = $21.60	$2.00 (+$2 one-time)	$153.80
Plivo Voice API, from EEA, major networks, 60/60	4,200 × $0.0359 = $150.78	1,800 × $0.0135 = $24.30	None listed	$175.08 in usage, inside a $1,000/month minimum commit
Twilio, EEA caller ID, rounded up to the minute	4,200 × $0.0420 = $176.40	1,800 × $0.0283 = $50.94	$2.70	$230.04
Vonage, domestic origin, per second	3,500 × $0.10039 = $351.365	1,500 × $0.01173 = $17.595	$2.44 (+$2.44 initial)	$371.40
sipgate Flow API (euros, excluding VAT)	Small package: €249.95 for 2,500 minutes, then 2,500 × €0.099 = €247.50; €596.45 if each started minute counts (6,000)			€497.45 to €596.45, no separate speech charge listed

Four things move these totals more than the rate cards suggest. The mobile share is the biggest: at 90% mobiles instead of 70%, every US-dollar API’s total rises, and Vonage’s rises most because its mobile rate is the highest of the four US-dollar APIs. The caller ID is next: the same 4,200 mobile minutes on Twilio with a US number would cost 4,200 × $0.3763 = $1,580.46 instead of $176.40. Billing increments are third: Vonage bills per second, so its 5,000 talk minutes stay 5,000, while the three 60/60 providers bill 6,000. Plivo’s SIP trunking product is the fourth: it prices German mobiles from Europe at $0.0324 on the major networks and bills “all major international destinations” at 1/1, though it adds that “Some international destinations may be at 60/60”. On per-second billing the same workload would be 3,500 × $0.0324 + 1,500 × $0.0096 = $127.80, still inside the Enterprise plan.

The bill counts answered calls only, and outbound dialling also places calls nobody answers. Telnyx and Plivo both publish surcharges for that. Telnyx adds $0.005 to every abandoned call (one the caller hangs up while it is still connecting or ringing, including calls to disconnected numbers) once more than 20% of a month’s outbound calls are abandoned. Plivo adds $0.005 per abandoned call above a 20% monthly threshold and $0.015 per call of 6 seconds or less above 10%, on both its Voice API and SIP trunking.

sipgate is not like-for-like. Its Flow API handles speech-to-text and text-to-speech and its price list shows no separate charge for them, while the other four price or provision speech separately (Plivo, for example, lists text-to-speech at $0.0000/min and speech recognition at $0.02 per 15 seconds), and the Flow page says it is billed “minutengenau” without defining rounding, so we show both readings. For a two-vendor version of this arithmetic on US rates, see our Twilio vs Telnyx cost comparison for AI voice agents.

Do you need a German address for a +49 number?

For a geographic (local) number, yes. The Bundesnetzagentur’s Verfügung 25/2006, consolidated as in force from 30 July 2026, says the area code of a local number allows a conclusion about the subscriber’s geographic location. It sets two ways to establish it: the location of the network access on the subscriber’s premises, permanently inside the local area; or the subscriber’s residence or business seat (“Wohnsitz oder Betriebssitz”) inside the local area. Where residence or business seat is the test, providers must check it when the contract starts and while it runs, for example against an identity card, a registration certificate, a commercial-register extract or a trade registration. If the residence or seat leaves the area, the right to use the number lapses. A provider that cannot ensure this local link may not hand out local numbers, but it may hand out national subscriber numbers instead. As a rule, the Bundesnetzagentur says it will order the provider to switch off a local number allocated without the local link, or still used after the link has gone.

Your situation	Twilio	Telnyx	Vonage	sipgate
German business with an address in the number’s area	Local number; commercial-register extract, trade licence or tax-office letter as proof	Local number; registration form, company certificate, utility bill under 3 months old; about 72 hours to validate	Landline on request; ID or business registration as proof of local address	Local numbers from your own area code after address verification
Business with a German address elsewhere in Germany	Mobile number (“Must be within Germany”)	National number (address in Germany)	Its overview lists only the landline, which needs proof of local address	Local numbers for the area of the address you verify
No address in Germany	Every number type these four document needs an address in Germany. Telnyx prices German mobile numbers, but its requirements article does not cover them, so ask Telnyx. Otherwise use an EEA number you hold elsewhere for EEA rates (Telnyx’s EEA origin list excludes UK +44 numbers), and check the 1&1 caveat in the next section.
Individual, not a business	Local and mobile: “not available to individuals”	Allowed with ID and the registration form	ID copy accepted for individuals	Not stated on the pages we read

Two vendor rules sit on top of the regulator’s. Vonage says that “If more than three (3) telephone numbers are requested for an end customer contract, the end customer must provide proof of need”, and that more than one hundred numbers require a certificate of need submitted to the Bundesnetzagentur. Telnyx says end users “must be physically present in the country when purchasing numbers from that country”, with EU passports and identity cards from any member state treated as local. Plivo lists no German numbers in its documentation, its Germany number-pricing data or its SIP coverage page, as at 12 November 2026. For how long document reviews of this kind take at Twilio and Telnyx, see our guide to UK and Australian number KYC bundle review times.

Does a German caller ID survive a call routed from abroad? TKG §120

Not reliably, and the law is the reason. TKG §120(4) requires every provider involved in a call to ensure that a German national number is shown as the caller’s number only if the call is handed over from the German public telephone network. If a call showing a German number is handed over from a foreign network, the providers must mark the route by which it entered the German network and suppress the number display. International mobile roaming is exempt, and the person called must be able to reject calls with a suppressed number easily and free of charge. Separately, §120(1) requires providers of publicly available number-based interpersonal communications services that let end users make outgoing calls to transmit a complete German national number as the caller’s number, and that number must be assigned to the end user for the service making the call. Under §120(2), an end user may also set an additional caller number only if it holds a right of use for that number and it is a German number (on call forwarding, the original caller’s number may be passed on instead); the Bundesnetzagentur may set conditions under which a foreign number is allowed.

Each provider’s own guidance tracks this rule:

• Twilio’s Germany voice guidelines say: “Outbound calls from Twilio Germany phone numbers should go through Twilio network, otherwise calls may not work.”
• Vonage’s Germany page says customers “must purchase a Vonage number to be able to make domestic in country voice calls”, and that “The operator 1&1 will block international CLI from reaching their own network subscribers.” Its general article warns that calls with a caller ID from the destination country “might stop working without prior notice”, and lists Germany among the countries where Vonage has access to local exchanges and operators.
• Telnyx rejects international caller-ID spoofing (“calls will be rejected as we, and many of the downstream carriers, do not support international spoofing”) and requires a real, dialable caller ID on calls into the EEA.
• sipgate’s Flow API uses the number configured on the Flow as the caller ID for outbound calls, and outbound calls “are only available upon request and after a positive review by sipgate support”.

The practical test is simple: present a German number that the provider assigned to you, on a call that the same provider hands into the German network. Number display matters on sales calls too: TDDDG §15(2) bars advertising callers from suppressing it, as our UWG guide explains. Forwarding inbound calls under a foreign caller ID has its own failure mode, covered in our page on Spanish and French forwarded caller IDs being blocked.

Which voice APIs offer EU data residency for German calls?

Each provider scopes its European option differently:

• Telnyx processes requests sent to api.telnyx.eu at its EU point of presence in Frankfurt, and Telnyx tells users to set a Frankfurt, London or Amsterdam AnchorSite to receive Voice API calls in Europe. Storage is a separate control: setting Data Locality to Germany, which Telnyx calls “an account-level, one-time, irreversible choice”. Telnyx says processing location “is not contractually guaranteed” because of failover, while the storage guarantee is contractual.
• Twilio offers an Ireland (IE1) region in Dublin for Programmable Voice. Numbers are bought in US1 and then re-routed to IE1, and features including Verified Caller IDs and BYOC trunks with static IP addresses are not yet supported there. Twilio warns that “During this initial phase of the rollout of Twilio Regions, Twilio doesn’t guarantee that all data will remain within your selected Region.”
• Vonage routes Voice API calls through api-eu-4 (Frankfurt) or api-eu-3 (Dublin), and says “user data from one geo-location is not accessible in another due to compliance requirements.”
• sipgate runs its data centres in Frankfurt and Düsseldorf, says on its price page that its infrastructure and servers are located exclusively in Germany (“ausschließlich in Deutschland”), and describes Flow as “EU-hosted, and operated by sipgate in Germany”.
• Plivo documents US and India data regions, and lists Frankfurt among its media and callback server locations.

Region settings cover what the provider stores and processes. They do not cover your speech, model and storage vendors, which need their own EU options before a German deployment can be described as EU-resident.

The +49 Origin Rule: how to choose

Read down this table until a row matches you; the right-hand column is the provider the published facts point to.

If this is true	Then
You want an agent that calls, follows up and books, not a voice stack to build	Zian, or LeadsNow.ai if you want it run for you
You have a German address, mostly call mobiles, and want the lowest list rate	Telnyx: $0.0310 a mobile minute including its fee on its own German number ($0.0221 from another EEA country’s number)
You need per-second billing for many short calls	Vonage (its mobile rate is $0.10039), or Plivo SIP trunking on the Enterprise plan, which bills major international destinations at 1/1
Call data must be processed and stored in Germany or the EU	Telnyx with api.telnyx.eu and Data Locality set to Germany (storage contractual, processing subject to failover), or sipgate (servers only in Germany)
You want a German carrier that handles speech for you, and can wait for an outbound review	sipgate Flow
You already spend $1,000 a month with Plivo	Plivo SIP trunking at $0.0324 a major-network mobile minute from Europe
You have no address in Germany	None of the five documents a German number without one; present an EEA number you hold, and expect 1&1 to block international caller IDs to its subscribers

The decision rule in one sentence: price a German outbound minute from the caller ID you can legally present inside Germany, because that number, not the destination, sets the mobile rate.

Frequently asked questions

Which voice API is cheapest for calling German mobiles?

Of the five we compared, on list rates read on 12 November 2026 with a German or EEA caller ID, Telnyx is lowest at $0.0310 a minute from its own German number, or $0.0221 from another EEA country’s number, including its $0.002 Voice API fee. Plivo charges $0.0359 to the major networks on its Voice API and $0.0324 on SIP trunking, both inside a $1,000-a-month Enterprise plan. Twilio charges $0.0420, Vonage $0.10039 billed per second, and sipgate’s Flow minute, with no separate speech charge listed, 6.9–9.9 euro cents.

Why does my caller ID change the price of a call to Germany?

European networks charge more to terminate calls from outside Europe. Twilio’s article on origin-based pricing for European destinations says “Origin is determined by the caller ID of the call”, so a German mobile minute costs $0.0420 from an EEA number and $0.3763 from a US one.

Do I need a German address to get a +49 number?

For a local number, yes. The Bundesnetzagentur’s local-number rules (Verfügung 25/2006) tie it to a network access, residence or business seat inside the area code’s local area. Twilio’s mobile numbers and Telnyx’s national numbers still need an address in Germany.

Can I show a German number on calls placed from outside Germany?

Not reliably. TKG §120(4) says a call showing a German number that is handed over from a foreign network must have its number display suppressed; international mobile roaming is exempt. Use a German number assigned to you, carried into Germany by the same provider.

Which voice APIs can keep German call data in the EU?

Telnyx (Frankfurt endpoint plus a Germany Data Locality setting), Twilio (Ireland IE1 region, with listed feature gaps), Vonage (Frankfurt or Dublin endpoints) and sipgate (Frankfurt and Düsseldorf). Plivo documents US and India data regions. Telnyx says EU processing is not contractually guaranteed, and Twilio says it does not yet guarantee all data stays in the selected region.

Is AI cold calling to Germany legal?

Only with the right consent: sales calls to consumers need prior express consent under UWG §7(2), and AI callers may need it for businesses too. Our UWG guide covers the detail and the Bundesnetzagentur’s fines.

Where every figure on this page comes from

Figure	Who published it	Link	Date read
Twilio Germany outbound $0.0283 landline, $0.0420 mobile from EEA, $0.3763 mobile; local $1.35/mo, mobile $30.00/mo; “current as of October 2026”	Twilio	Programmable Voice Pricing in Germany	12 Nov 2026
Twilio prefix groups +491570, +49700, +49701 at $0.3763; EEA origin prefixes	Twilio	Outbound voice prices CSV	12 Nov 2026
Twilio German mobile numbers domestic-voice-only; address required	Twilio	Number prices CSV	12 Nov 2026
Twilio German address and document rules; toll-free via the Bundesnetzagentur	Twilio	Germany: Regulatory Guidelines	12 Nov 2026
Twilio: German numbers “should go through Twilio network”	Twilio	Germany: Voice Guidelines	12 Nov 2026
Twilio origin determined by caller ID; EEA country list	Twilio	Origin-Based Pricing for European destinations	12 Nov 2026
Twilio rounds partial minutes up	Twilio	How Are Twilio Voice Call Duration Minutes Calculated for Billing?	12 Nov 2026
Twilio IE1 region, unsupported voice features	Twilio	Regional product availability	12 Nov 2026
Twilio data-residency caveat	Twilio	Twilio Regions	12 Nov 2026
Twilio numbers bought in US1, re-routed to IE1	Twilio	How to Route a Twilio Phone Number to AU1 or IE1 Region	12 Nov 2026
Telnyx Germany outbound rows: $0.0081/$0.0201 from EEA, $0.0251 Telefónica from EEA, $0.01/$0.029 Local, $0.1694 Mobile Other Local, $0.0231/$0.0401 default, $0.0462 Telefónica default, $0.5375 High Surcharge; 60/60	Telnyx	Public pricing API, elastic-sip-outbound (rate deck behind telnyx.com/pricing/elastic-sip)	12 Nov 2026
Telnyx $0.002/min Voice API fee; German number rental and one-time costs	Telnyx	Telnyx Pricing for AI Agents (pricing.md)	12 Nov 2026
Telnyx Germany number documents, physical presence, ~72 hours	Telnyx	Germany DID Requirements	12 Nov 2026
Telnyx PAI requirement into the EEA; no international spoofing	Telnyx	Caller ID Number Policy	12 Nov 2026
Telnyx Local origination = a number of the called country bought on Telnyx; EEA origination = another EEA country’s number	Telnyx	Updates to Global Conversational Rate Deck	12 Nov 2026
Telnyx $0.005 abandoned-call surcharge above 20% abandoned outbound calls	Telnyx	Surcharge for High Abandoned Call Rates	12 Nov 2026
Telnyx 60/60 billing increments	Telnyx	Billing increments	12 Nov 2026
Telnyx Frankfurt EU PoP, Data Locality, processing not contractually guaranteed	Telnyx	Regional Endpoints & the EU PoP	12 Nov 2026
Telnyx Frankfurt, London, Amsterdam AnchorSites	Telnyx	Voice API Services in Europe	12 Nov 2026
Vonage Germany outbound $0.01173, $0.07222, $0.10039, $0.14431, $0.66871 and $2.79287 (Remote Countries and Non-CLI); billing 0s/1s and 1s/1s; number $1.22 + $1.22; toll-free $7.27; effective 7 and 9 July 2026	Vonage	Vonage voice price sheet (USD)	12 Nov 2026
Vonage German landline on request, 1–3 business days, proof of need above three numbers, certificate above 100	Vonage	Voice Numbers Features Overview	12 Nov 2026
Vonage domestic calls need a Vonage number; 1&1 blocks international CLI	Vonage	Germany Voice Features and Restrictions	12 Nov 2026
Vonage local-CLI calls “might stop working without prior notice”	Vonage	In-Country, Local, or No-CLI Calls Rejected	12 Nov 2026
Vonage per-second billing	Vonage	How does voice pricing work for inbound and outbound calls?	12 Nov 2026
Vonage api-eu-3 Dublin, api-eu-4 Frankfurt	Vonage	Regions	12 Nov 2026
Plivo Voice API Germany $0.0135, $0.0359, $0.0495, $0.3850, $1.0674	Plivo	Germany Voice API Pricing	12 Nov 2026
Plivo SIP trunking Germany $0.0096, $0.0324, $0.0460, $0.3820; 1/1 for major destinations	Plivo	SIP Trunking Pricing, Germany	12 Nov 2026
Plivo: no inbound number types for Germany	Plivo	SIP Coverage, Germany	12 Nov 2026
Plivo pay-as-you-go covers US and India; Enterprise from $1,000/month	Plivo	Pricing	12 Nov 2026
Plivo number countries by plan; $1,000/month minimum commit	Plivo	Numbers overview	12 Nov 2026
Plivo Voice API 60/60 billing	Plivo	Billing Concepts	12 Nov 2026
Plivo US and India data regions; abandoned-call ($0.005 above 20%) and short-call ($0.015 above 10%) surcharges	Plivo	Account Limits	12 Nov 2026
Plivo Frankfurt media and callback servers	Plivo	Firewall & Network Configuration	12 Nov 2026
sipgate Flow packages €249.95 to €3,499.95, 9.9 to 6.9 ct; prices excluding VAT; Frankfurt and Düsseldorf data centres	sipgate	sipgate Flow API	12 Nov 2026
sipgate Flow outbound on request after review; Flow number used as caller ID; EU-hosted	sipgate	sipgate flow documentation	12 Nov 2026
sipgate 3 numbers €4.95/month	sipgate	sipgate Preise	12 Nov 2026
sipgate local numbers need a verified fixed address in Germany	sipgate	Ortsrufnummern	12 Nov 2026
Local-number location criteria; national numbers as the alternative; switch-off; in force from 30 July 2026	Bundesnetzagentur	Verfügung 25/2006 (consolidated)	12 Nov 2026
TKG §120(1), (2) and (4): number assignment, additional caller numbers, display suppression for calls handed over from abroad, roaming exception	Federal statute (text as published by dejure.org)	§ 120 TKG Rufnummernübermittlung	12 Nov 2026
Zian: 30+ languages including German	Zian	zian.ai Features + Integrations page, FAQ “What languages are supported?”	12 Nov 2026
Worked monthly bill (3,000 calls, 5,000 talk minutes)	zian.ai calculation from the rates above	This page	12 Nov 2026