Formats
Introduction
This document guides the user through the different formats that are required to successfully request data from T-Mobile's APIs.
Input/Output Format
Both the request body and response data are formatted as JSON for all APIs.
Date Format
Timestamps for Call Verification and Fraud Prevention (both those sent in requests and those returned in responses) should be formatted as shown in our API examples. We support RFC 3339 timestamps. The preferred way to pass in a date is by converting the time to UTC such as this: 2013-04-17T09:12:36-00:00.
In cases where timestamps are rounded to a given day, you may omit the time component, so instead of 2013-04-17T13:35:01+05:00 you can use 2013-04-17. However, if a time and not just a date is specified in a request then the calendar date in the Pacific timezone at the moment specified is the day that is accepted.
T-Mobile supports the subset of dates after the start of the Unix epoch 1970-01-01T00:00:00+00:00 00:00:00 UTC on January 1.
Protocols
All protocols for T-Mobile APIs are in HTTPS.