> For the complete documentation index, see [llms.txt](https://postman-v2.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v2.guides.gov.sg/postman-v2-admin-portal-for-ui-users-internal/how-do-i-onboard-postman-v2-internal-sms/2.-sign-up-for-a-twilio-account.md).

# 2. Sign up for a Twilio account

How do I get started with Twilio?

{% hint style="info" %}
Unlike Postman V1 (Legacy Postman), agencies will no longer need to submit the SMS onboarding form. Please directly apply for an account with Twilio, and work with them to have your registered sender IDs tagged to your accounts.

Postman **does not** manage Twilio accounts on behalf of agencies. 
{% endhint %}

### Before creating a Twilio account

You will need the following before signing up for a Twilio account:

1. Email address: This email address will be associated with the Twilio account that you are signing up for
2. Mobile Number: This number will be receiving security codes required when logging into your Twilio account. 
3. [Complete your sender ID registration](/postman-v2-admin-portal-for-ui-users-internal/how-do-i-onboard-postman-v2-internal-sms/1.-sender-id-registration.md)

### Creating a Twilio account

1. Refer to Twilio's documentation on how to [sign up for your free Twilio trial](https://www.twilio.com/docs/messaging/guides/how-to-use-your-free-trial-account#sign-up-for-your-free-twilio-trial) to use their messaging service.
2. Upon signing up for a free account on Twilio, you will be taken to your Twilio Console Dashboard Homepage. 

<figure><img src="https://862051585-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl3mC1ibWq8HG4BKl4qlL%2Fuploads%2FRQoVLb3liAgbZ6710FrS%2FScreenshot%202024-03-20%20at%2011.52.27%20AM.png?alt=media&amp;token=8eb6db31-f736-4ef1-9295-e5bb0bdcb10d" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://postman-v2.guides.gov.sg/postman-v2-admin-portal-for-ui-users-internal/how-do-i-onboard-postman-v2-internal-sms/2.-sign-up-for-a-twilio-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.