- API & Docs
When a message comes in to one of your Twilio numbers, Twilio makes an HTTP request to the message URL configured for that number. In your response to that request you can tell Twilio what to do in response to the message.
Twilio behaves just like a web browser, so there's nothing new to learn.
Cookies: Twilio accepts HTTP cookies and will include them in each request, just like a normal web browser.
Redirects: Twilio follows HTTP Redirects (HTTP status codes 301, 307, etc.), just like a normal web browser.
Caching: Twilio will cache files when HTTP headers allow it (via ETag and Last-Modified headers) and when the HTTP method is GET, just like a normal web browser.
Twilio will keep cookie state across multiple SMS messages between the same two phone numbers. This allows you to treat the separate messages as a conversation, and store data about the conversation, such as a session identifier, in the cookies for future reference. Twilio will expire the cookies for that conversation after four hours of inactivity.
Twilio does the right thing when your application responds with different MIME types.
|text/xml, application/xml, text/html||Twilio interprets the returned document as a TwiML XML Instruction Set. See the XML Verbs section for details. This is the most commonly used response.|
|text/plain||Twilio returns the content of the text file to the sender in the form of a message.|
When your application responds to a Twilio request with XML, Twilio runs
your document through the TwiML interpreter. To keep things simple, the
TwiML interpreter only understands a few specially named XML elements.
In TwiML parlance these are divided into three groups: the root
<Response> element, "verbs" and
"nouns". Each group is discussed below.
The interpreter starts at the top of your TwiML document and executes instructions ("verbs") in order from top to bottom. As an example, the following TwiML Message snippet sends "Hello World" as a message reply to the sender before redirecting control to the TwiML at https://demo.twilio.com/sms/welcome.
<?xml version="1.0" encoding="UTF-8" ?> <Response> <Message>Hello World!</Message> <Redirect>https://demo.twilio.com/sms/welcome</Redirect> </Response>
You can provide multiple
<Message> verbs in one TwiML document to send
multiple messages. For example:
<?xml version="1.0" encoding="UTF-8" ?> <Response> <Message>This is message 1 of 2.</Message> <Message>This is message 2 of 2.</Message> </Response>
TwiML elements ("verbs" and "nouns") have case-sensitive names. For example,
<message> instead of
<Message> will result in an error. Attribute
names are also case sensitive and camelCased. And you can use
XML comments freely; the interpreter ignores them.
The root element of Twilio's XML Markup is the
<Response> element. In any
TwiML response to a Twilio request, all verb elements must be nested within
this element. Any other structure is considered invalid.
<?xml version="1.0" encoding="UTF-8"?> <Response> <Message>I'm hungry!</Message> </Response>
Most XML elements in a TwiML document are TwiML verbs. Verb names are case sensitive, as are their attribute names. There is only one core TwiML Message verb and one secondary verb, with detailed documentation on each. The core verb is:
<Message>: Send a message in reply to the incoming message.
Note that there are certain situations when the TwiML interpreter may not reach
verbs in a TwiML document because control flow has passed to a different document.
This usually happens when a verb's 'action' attribute is set. For example, if an
<Message> is followed by a
<Redirect> is unreachable if the
<Message> verb's 'action' URL is set. In this case, SMS session flow continues
with the TwiML received in your response to the 'action' URL request.
A Noun in TwiML is anything nested inside a verb that is not itself a verb. It's
whatever the verb is acting on. This is usually just text. But sometimes, as in
the case of
<Message> with its
<Body> nouns, there are nested XML
elements that are nouns.