Join the waiting listJoin
Products
Company
About TelyneWho operates the platform. White labelSell under your own brand. Who it is forSix kinds of business.
Join the waiting list Sign in Explore the platform
Home/Capabilities/Developer platform/API explorer

An interactive API explorer
for the call before the code

Fill in the fields, send the request, read the response, from the browser, against the sandbox, with your own test key. The explorer is rendered from the published specification, so what it offers is what exists.

Start in the sandbox See how it works

Sandbox profiles are simulated and cost nothing. No card, no commitment.

Join the waiting list for production access

Fill it in. Send it. Read it.

Five things the explorer does that a documentation page cannot.

RENDERED FROM

The OpenAPI spec

SENDS TO

Sandbox Live

AUTH

Your test key

SHOWS

Request and response

EXPORTS

curl Your language
Your requestYour fields, your key, your response
POST /v1/esimsandbox · sk_test_
RENDERED FROMthe published spec
EXPORTS AScurl, ready to paste

# What the explorer sends, verbatim
POST /v1/esim  { "source": "openapi", "target": "sandbox", "auth": "sk_test_", "shows": "both", "export": "curl" }

BEFORE ANY CODE

Reading about a call is not the same as making one.

What happens between opening the explorer and having something that works in your editor.

OPEN

Pick an endpoint

Every one the specification describes, with its fields and their types already there.

FILL

Enter the values

Validated against the specification before it is sent, so a mistake is caught in the form.

SEND

It is a real call

To the sandbox, with your test key, returning a real object rather than a sample.

COPY

Take it away as curl

Or as a snippet in your language, which is where the integration actually starts.

Nothing in the explorer is a mock-up of the API. It is the API, with a form in front of it.

WHO IT IS FOR

For the first hour, and for every hour after

Evaluating an API by reading it is slow and unreliable. Calling it is neither, and it should not require a project to do so.

Anyone evaluatingAnswer whether it fits by trying it rather than by reading about it.
Support and solutionsReproduce a customer's call exactly, without a local environment.
Non-engineersProduct and operations people who need to see an object, not a description of one.
Anyone debuggingIsolate whether the platform or the client is at fault, in one request.
No local setupIt runs in the browser
No sample dataReal sandbox objects
No driftRendered from the spec
No dead endExports as code

The shortest path from question to answer. Send a call from the browser today, at no cost.

Start in the sandbox Join the waiting list

WHAT YOU GET

A form in front of the real API, not a description of it

Every endpoint, every field and every type comes from the published specification, so the explorer cannot offer something the platform does not have.

THE CAPABILITY
Coverage
Every endpoint the specification describes, which is every endpoint there is.
Validation
Fields are checked against the specification before the request is sent, so mistakes are caught in the form.
Environment
Sandbox by default with your test key, so exploring cannot issue anything real by accident.
Response
The actual object, with the actual fields, rather than an illustrative sample.
Export
The same call as curl or as a snippet, ready to paste where the work continues.
BUILDING ON IT
Keys
Your own prefixed test key, so what you see is what your integration will see.
Retries
Idempotency headers can be set in the form, so the behaviour can be rehearsed rather than read about.
Errors
One shape everywhere: a type, a code, a message, the parameter at fault and a link. Never a bare 500 with a stack trace.
Reference
One published OpenAPI specification. The server validates against it, the SDKs are generated from it and the sandbox mocks from it.

WORKS WITH

Switch on the next one the same way

Nothing new to sign and nothing new to integrate. The same call with a different noun.

DocumentationRendered from the same specification. SandboxWhere every exploratory call lands. REST APIWhat the form is a front end for.

QUESTIONS

API explorer on Telyne

Are the calls real?

Yes. The explorer sends an ordinary API request with your own test key and returns the actual object. It is the API with a form in front of it, not an illustration of it.

Can I accidentally create something live?

Not by default. The explorer targets the sandbox with a test key, and a test key cannot reach live resources. That boundary is enforced by the platform.

Where do the fields come from?

The published OpenAPI specification, which is also what the server validates against. The explorer cannot offer a field that does not exist or omit one that does.

Can I take the call away with me?

Yes, as curl or as a snippet in your language, with the values you used. That is usually where the integration actually begins.

Do I need to install anything?

No. It runs in the browser, which is the point: evaluating an API should not require a local environment first.

Join

Send a real call before you open an editor

No approval step and nothing to sign. The sandbox is open now, and production access opens in the order requests arrive.

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.