Getting Started with your SignalWire Space

Get familiar with the SignalWire interface

By John Foland, Developer Evangelist

Hi my name is John Foland and I am the developer evangelist here at SignalWire.

Today I'd like to talk about the power intrinsic to the SignalWire cloud and to do so I'd like to do a general overview of SignalWire itself and go over some of the key core concepts and notions that are important to developing with SignalWire but also familiarize you with the SignalWire space and interface. Now this is the first of a series of videos that I'll be doing where I'm going to go into a technical deep dive of each and every subject that we attack here but today is an overview video so we'll keep it short and simple.

So as you can see here, we are logged in to the SignalWire space interface and one of the first things that I'd like to talk to you about is the notion of projects within the context of SignalWire. Projects are a great way to separate your application development and clients and a great way to break apart your account. One of the more obvious benefits of using projects is to separate usage out for clients. I'd also like to have you note that all of the menu items here on the navigation to the left anything that's underneath the project heading, these all pertain to the current project whichever project we have pulled up and underneath the space heading those apply all globally to the SignalWire account.

Now when developing a full-fledged application with conditionals and your own business logic and maybe even external data sources, SignalWire offers two main ways of doing that. the RELAY family of a APIs and the LaML API's. Now I will go into which is better in specific contexts in a future video but I just wanted to point out that the RELAY and the LaML tabs are where you want to go to see your activity for the usage of those API's and it's also in the main tabs here it's also a good place to get direct links to the API documentation. The same thing is true for RELAY.

So you can see here I'm on the sip endpoints page, now nothing too complicated here, I have a list of all of my active endpoints I now nothing too complicated here I have a list of all of my active endpoints I can configure them I can create a new one also have under the sip settings here now these apply these sip profile settings apply to all of the sip endpoints in my project. I gave it a fancy end quite appropriate slug in the SIP URI for all the endpoints in my in my overview project but nothing nothing too complicated here. Now here Dialogflow is actually a Google tool that allows you to rapidly create these artificially intelligent robots essentially based on artificial intelligence that allows you to create a conversational interface. What's super interesting in the context of SignalWire is that we allow you to import one of those Dialogflow agents. For example you could have someone call a phone number and they could and for example you could have someone call a phone number and they could interact with that Dialogflow agent, that that robot, that you that you built with the Dialogflow tool. So in this page you could connect and you can import an existing Dialogflow agent that you have associated with your account and you can also see the logs anything that comes out from anything that comes out from those agents that you've imported.

Here on the integrations page you can set up new integrations or manage existing integrations, basically integrations are other platforms or services that are specifically set up to be used with SignalWire. Most likely unless you already have an integration that you’re looking to connect twisting the wire you probably won't need this but I'll just give you a quick look at some of the integrations that we proposed already. This new zapier integration might even interest you it's in beta but it's definitely worth taking a taking a look at.

Now here on the API page on the API credentials page I can create and manage the tokens that I'll be using in my various SignalWire projects. These tokens are project specific, so my overview token is specific to my overview project and these you'll use in a number of different places whether they be inside the apps that you create with RELAY or LaML or whether you're using some other third-party integration these API tokens are essentially the login credentials that you'll need for your app to be able to speak with SignalWire.

Now one of the coolest and most fun things to do with a SignalWire space is to buy and manage phone numbers, and phone numbers also kind of act as a hub of a lot of the activity that you do on SignalWire. Why don't we make one together, I'm going to click here, add a new phone number. One of the cooler things that I like about this interface is obviously it's cool local local toll-free shortcode but I love being able to search for my name. I'm gonna say I want my phone number to end with my name so you know what you would see on a numerical keypad. Now this should give me a bunch of phone numbers that end in five six four six, yep JOHN

And you know what I'm gonna take this Michigan number here and like that it is purchased. Now as soon as I purchase a phone number, I have my phone number settings where I could hook it up to LaML or RELAY or any of our other integrations like Dialogflow, but here I'm just gonna name there we go. And there we have it, I have a new phone number all purchased and ready to go. 

I truly hope that this video has been useful and helpful for you, I'd also love to know what you're developing so please reach and let us know what you're doing with SignalWire or if you have any questions if you feel stuck anywhere. The best place for all of those resources is our community slack forums. SignalWire OGs are standing by 24/7 and lots of members of the community as well. So until next time!