Trestle’s response times vary based on the product. This is because each query has a different response set, impacting the response times significantly. Depending on the placement in the waterfall, each customer can also experience different response times. The times below are based on Trestle’s measurements across all their customers. First, here are the definitions:
- P50: Average response time of the API. In other words, 50% of the queries will be served within this time.
- P95: 95% of the queries will be served within this time.
| API | P50 | P95 |
| Reverse Phone API | 100 mSec | 300 mSec |
| Smart CNAM API | 100 mSec | 100 mSec |
| Caller Identification API | 100 mSec | 100 mSec |
| Phone Validation API | 250 mSec | 500 mSec |
| Real Contact API | 250 mSec | 500 mSec |
| Find Person API | 150 mSec | 300 mSec |
| Reverse Address API | 150 mSec | 300 mSec |
Finally, the response times are measured within its firewall – from the moment the query hits its servers and the response is sent back out. Trestle’s APIs are housed in the U.S.-West region, so adjust the response time expectations based on where your service is hosted. A general rule of thumb is 150 mSec round trip, coast to coast, as the wire time.