As you develop applications using Twilio Runtime, Services can help you organize the Functions and Assets that compose each respective application, keep separate Environments, and control Deployments.
You will be prompted to provide a name for the new Service. Click Next once you're satisfied with the new Service name.
The Service will be bootstrapped, and you'll be redirected to the Functions Editor shortly after. There, you can begin adding Functions and Assets.
A Service name must be fewer than 50 characters, and may only contain letters, numbers, and dashes.
Once selected, the Service name is permanent and cannot be modified.
The name of your Service directly influences the domain that your Functions and Assets will be deployed to. The general URL scheme for a Service is as follows:
https://[service name]-[random numbers]-[environment].twil.io/
This means that a Service named
astley will have the following domain by default:
https://astley-3432.twil.io/ # The default, production URL
It could potentially also create these other, Environment-specific domains depending on how you name them and which you choose to deploy:
https://astley-3432-dev.twil.io/ # For an Environment named 'dev' https://astley-3432-test.twil.io/ # For an Environment named 'test' https://astley-3432-stage.twil.io/ # For an Environment named 'stage'
You can view all of your existing services on the Services page in the Twilio Console.
For each existing Service, you can:
- Click on the unique name to visit the Functions Editor for that Service and view all Functions and Assets
- Click on Service Details to view meta data for the Service and all Functions, Assets, and Environments
- Click on Delete to begin the process of deleting the Service
Clicking on Delete will initiate the process of deleting a Service. First, you will be prompted to verify that you indeed wish to delete the Service. After confirming, the Service and all of its child Functions, Assets, and Environments will be deleted.
If the Service is being used by another application like Studio or Flex, those applications will no longer be able to reach the Service and associated Functions or Assets. This poses the risk of breaking dependent applications, and should be taken into consideration before deleting a Service.
There is currently a maximum of 50 Services available to each Runtime user by default. Once you reach 50 Services, you will no longer be able to add additional Services without deleting an existing Service.
Functions(Classic) does not support Services. If you are using Functions(Classic), you can create functions directly in the editor and attach compatible Assets from Assets(Classic).