SUPPLY TO TELYNE
A telecom supplier integration
you do not have to build
If you run a telecom API and you are looking for distribution, this page is for you. A supplier integration here means we take your API as it stands, carry it on our platform under our own account, and put it in front of customers you would not otherwise take on. You build nothing and you change nothing.
Three things from you, and the third is a test account.
WHO THIS IS FOR
You already have the network. The gap is distribution
Three shapes of supplier, and the same offer to each. What differs is what you are short of.
WHAT WE ASK FOR
Three things, and a fourth would be our failure
We integrate against what you already have. If this list grows, the design is wrong on our side and it gets fixed on our side.
THE FIRST ARGUMENT
The supplier builds nothing and changes nothing
Every integration is a negotiation about who absorbs the difference between two systems. Here it is us, every time.
A platform that wants to carry your API usually asks you to meet it somewhere. A webhook in their format. A field renamed. An endpoint that exists only for them. Each request is small on its own, and together they are engineering you did not plan, for revenue you have not seen yet.
We do not ask. Telyne adapts to the supplier, never the reverse. Your API keeps the shape it has, awkward parts included, and turning it into ours is work we do and then maintain. If you ship a breaking change it is ours to absorb, and we would rather hear about it early than be asked to approve it.
What to expect from us is questions, and a test account under load.
THE SECOND ARGUMENT
The accounts nobody signs one at a time
Not accounts that are bad. Accounts where the cost of signing one is the whole margin on it.
THE COMMERCIAL SHAPE
One account of record, and a line you are not on
Telyne signs the contract with you and is the account of record. Every sale flows through that one account, so what you see is a single customer whose usage grows, rather than a stream of accounts to open, invoice and chase.
That is the arrangement between you and us, and it stops there. Telyne buys from suppliers and sells to its own customers. What those customers charge their end users is theirs, on their own payment rails, and Telyne is not in it.
So there are two commercial relationships in view here and they do not meet: ours with you, and the one each of our customers holds with the people they serve.
HOW IT GOES
Four steps, and three of them are ours
What happens after you send the form, in the order it happens.
You tell us what you carry
The form below. What your API does, which markets it covers, and anything we should know before we look at it.
We come back to you
A person reads it and replies. If it is not a fit we say so plainly rather than going quiet.
We build against your sandbox
Credentials, your documentation and a test account. We write the adapter, and what comes back to you is questions rather than change requests.
It goes into the catalogue
The capability appears on the same key and the same invoice as everything else, in front of every account on the platform.
There is no number of days on step two, because nobody here has committed to one and inventing it would be the first thing we told you that was not true.
Tell us what you carry
One form, read by a person. Say what your API does and which markets it covers, and we will come back to you.
We use what you send to reply to you and for nothing else. We keep it for 12 months and then delete it.
Tell us what you carry
Send us the three things below and we will come back to you.
One email at launch. Nothing else, and unsubscribe in one click.
We send a link to confirm the address. Unconfirmed addresses are deleted after 30 days.
Complex requirement or an existing estate to move? Talk to us.