> For the complete documentation index, see [llms.txt](https://developers.evertransit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.evertransit.com/webhooks/quickstart-guide/configure-your-server.md).

# Configure your server

Learn to set up a server to manage incoming webhooks.

Now that our webhook is ready to deliver messages, we'll set up a basic Express server to handle incoming payloads.

### Writing the server <a href="#writing-the-server" id="writing-the-server"></a>

We want our server to listen to `POST` requests, at `/webhook`, because that's where we told EverTransit our webhook URL was. Because we're using `ngrok` to expose our local environment, we don't need to set up a real server somewhere online, and can happily test out our code locally.

Let's go inside the project created in the [Setup your server](/webhooks/quickstart-guide/set-up-your-server.md#creating-our-local-development-environment) section and set up a little Express app to do something with the information. Open the `index.js` file and copy and paste for our initial setup which might look like this:

{% code title="index.js" %}

```javascript
const express = require('express');
const PORT = 3000;

const app = express();

app.use(express.json());

app.post('/webhook', (req, res) => {
    const body = req.body;
    console.log(body);
    return res.sendStatus(200);
});

app.listen(PORT, () => {
    console.log(`Listening at port ${PORT}`);
});

```

{% endcode %}

Start this server up executing `node index.js` from your terminal.

Since we set up our webhook to listen for `ride.created` events, go ahead with your dispatch and create a new ride for testing purposes; you can cancel it later. Once you've created it, switch back to your terminal. You should see something like this in your output:

&#x20;

![](https://401638202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FncBJGr7LibzayGdNpU4o%2Fuploads%2F9s2MLLyBwhzoaNDYqF83%2FScreen%20Shot%202022-05-05%20at%2012.51.41%20PM.png?alt=media\&token=35ad434f-f7c8-455c-93f2-8a21238db6c1)

Success! You've successfully configured your server to listen for webhooks. Your server can now process this information in any way it sees fit.