It is always possible for your request to return an error. If an error o= ccurs, e.g. if your API username/password is incorrect, our wrapper will th= row a C# exception. If you're not familiar with handling exceptions in C#, = it basically means you need to put the wrapper function calls in a try-catc= h block as shown in the example:
try {
=09Hashtable result;
=09result =3D tmClient.sendSMS("My message", "447000000000&q=
uot;, "Sender", 72, "", "", null);
} catch(RestClientException e) {
=09Hashtable errors =3D tmClient.getLastErrors();
}=20
You must decide how to handle errors according to the logic of your part=
icular application.
For example, if you're building a web interface t=
o send text messages, and a send fails, you may wish to show a visual alert=
to the user.
Note that more than one error can be reported at once. =
Therefore although a single C# exception (the first of the errors) is throw=
n, the complete set of errors encountered is available in a Hashtable of ke=
y-value pairs. The key of each pair is the error code and the value is a de=
tailed description of the error.
foreach (DictionaryEntry de in tmClient.getLastErrors())
=09Console.WriteLine("Error {0}: {1}", de.Key, de.Value);=
=20
You must know!
=20 =20Our example code is an illustra= tion of how you might integrate with our systems and is not certified for p= roduction environments. You are responsible for testing and QA.