# Getting Started

> What the Edesy browser calling SDK does, the pieces you need, and the order to set them up.

Source: https://edesy.in/docs/webrtc/getting-started

To add browser calling to your app you need three things: an Edesy account at webrtc.edesy.in, a small token endpoint on your own server that calls Edesy with your API key, and either the drop-in dialer script or the JavaScript SDK on your page. Set them up in the order below.

## What you need

| Piece | Where it runs | Purpose |
|---|---|---|
| Edesy account | [webrtc.edesy.in](https://webrtc.edesy.in) | Softphone, call history and the Developers page with your API key |
| API key | Your server only | Authenticates calls to the token endpoint. Never ship it to the browser |
| Token endpoint | Your server | Calls `POST https://webrtc.edesy.in/api/v1/token` and returns the JSON to your page |
| Dialer or SDK | The browser | Registers with Edesy and places calls |

## Steps

1. **Sign in** at [webrtc.edesy.in](https://webrtc.edesy.in). Edesy uses one login across its apps.
2. **Try the softphone.** The Softphone page in the portal dials a real number from your browser, so you can hear call quality before writing code.
3. **Copy your API key** from the Developers page. Keep it server-side.
4. **Build a token endpoint** on your server. See [Token Endpoint](https://edesy.in/docs/webrtc/sdk/token-endpoint).
5. **Pick a front end.** The [drop-in dialer](https://edesy.in/docs/webrtc/drop-in-dialer) for zero code, or the [SDK](https://edesy.in/docs/webrtc/sdk/connect-and-call) for your own UI.
6. **Check your costs** on [Pricing](https://edesy.in/docs/webrtc/getting-started/pricing).

## Browser requirements

The SDK uses WebRTC, so the page must be served over HTTPS (or `localhost` while developing) and the user must allow microphone access when the first call starts.

## FAQ

### Do I need a phone or a desk handset?

No. The browser is the phone. The user needs a microphone and speakers or a headset.

### Can I put my API key in the front end?

No. Anyone can read browser code. Your server calls the token endpoint and passes only the short-lived token JSON to the page.

### What is the difference between the drop-in dialer and the SDK?

The drop-in dialer is a ready-made floating keypad added with one script tag. The SDK gives you `connect()`, `call()` and events so you can build your own buttons inside a CRM or support tool.

### Does it work on mobile browsers?

The SDK uses standard browser WebRTC and microphone APIs. Test the browsers your users have before you roll it out.

### Which numbers can I call?

Pass the number in international format without the plus sign, for example `919876543210` for an Indian mobile.

### Is there a free trial?

No separate free trial is offered for browser calling. Calls are paid from your prepaid Edesy wallet at the rate on the [Pricing](https://edesy.in/docs/webrtc/getting-started/pricing) page. For a guided walkthrough, [book a demo](https://edesy.in/demo).