Welcome to the Tatango v2 API! The Tatango v2 API is designed for developers, engineers, or anyone else who’s comfortable creating custom-coded solutions or integrating with RESTful APIS. If you’re not familiar with API concepts like HTTP response codes, REST endpoints, and JSON, try Zapier.

​
Authentication

Tatango authenticates API requests by validating an API key that must be passed with each API call. We use the built-in HTTP basic authentication scheme supported by most HTTP libraries. Use your login email as the username and the API key as the password. 
curl -u "your_email@example.com:your_api_key" https://app.tatango.com/api/v2/lists
Make sure to replace my_api_key with your API key, which can be obtained by logging into the Tatango App.
You can access your API key here.

​
Returning multiple results and pagination

By default, GET API calls that return multiple items in a list will return up to 10 items for a single call. The pages_count parameter in the returned JSON will indicate the number of “pages” included in the entire result set. (So for example, if a call to https://app.tatango.com/api/v2/lists finds 27 lists in the system, the JSON will include the following (see JSON snippet below): 
{
  "per_page":10,
  "count":27,
  "page":1,
  "pages_count":3
}
The pages_count parameter will default to 0 when there is no items in the list.
To fetch the next page of results, pass the page parameter on the URL, like this: https://app.tatango.com/api/v2/lists?page=2. You can also change the number of records returned in each “page” by passing in a “per_page” parameter as part of the URL, like this: https://app.tatango.com/api/v2/lists?per_page=50.
Note that the system will only allow up to 1000 records to be returned in a single call.

​
Carrier IDs

This section provides a list of carrier ID and names (US and Canada) for any response that includes carrier and carrierName.

​
United States Carriers

Carrier NameCarrier ID
1st Point (a.k.a. Shelcomm)11293
Aerialink11333
Alaska Communications Systems (ACS)592
Altice Mobile11359
ASTAC10242
AT&T383
Atlantic Tele-Network International (ATNI)10542
bandwidth.com (includes Republic Wireless)766
Bluegrass Cellular562
Boost628
Brightlink10212
Bristol Bay Telephone Cooperative11332
C Spire Wireless (aka Cellular South)386
Carolina West Wireless564
Cellcom587
Cellular One of N.E. Arizona566
Chariton Valley Cellular701
Chat Mobility619
Copper Valley Telecom802
Cordova10282
Cross Wireless618
Digital Communications Consulting11316
DISH Wireless12227
Duet Wireless696
East Kentucky Network (Appalachian Wireless)570
Enflick10262
GCI Communications603
Google Voice798
Illinois Valley Cellular574
Indigo Wireless11174
Inland Cellular575
Inteliquent10232
ISP Telecom12228
James Valley Cellular (JVC)11304
MetroPCS788
MTPCS Cellular One (Cellone Nation)655
Nemont CDMA796
Nemont UMTS873
Nex Tech Communications578
Northwest Missouri Cellular620
Panhandle Wireless626
Pine Belt10352
Pine Cellular580
Pioneer Cellular621
Plivo11620
Ring Central11638
Rural Independent Network Alliance (RINA)567
SouthernLINC763
Sprint34
Standing Rock Telecom764
T-Mobile79
Telnyx11351
TextMe11306
Thumb Cellular604
Tracfone556
Triangle Wireless10272
Truphone11318
TSG Global (Flex Talk)11671
Tychron12227
Union Telephone549
United States Cellular Corp56
United Wireless602
Verizon77
Viaero Wireless650
Virgin Mobile525
West Central Wireless559
Zipwhip11749

​
Canadian Carriers

Carrier NameCarrier ID
Aliant509
Bell Mobility80
Eastlink Wireless799
Execulink10573
Fido (Microcell)138
Fizz10638
Freedom / Wind653
Mobilicity654
MTS510
NorthernTel512
Rogers75
Sasktel102
SSI Micro11315
Telebec511
Telus70
Videotron615
Virgin Mobile537

​
Errors

The Tatango v2 API uses the following error codes:
Error CodeMeaning
400Bad Request — Your request is invalid.
401Unauthorized — Your API key is wrong.
403Forbidden — You are not authorized for this request.
404Not Found — The specified endpoint could not be found.
405Method Not Allowed — You tried to access an endpoint with an invalid method.
406Not Acceptable — You requested a format that isn’t JSON.
410Gone — The requested resource has been removed from our servers.
422Unprocessable Entity - There was a problem of some sort with either the JSON or request parameters you supplied. Usually, this error will be accompanied by a detailed description of the problem.
429Too Many Requests — You’re requesting too many resources! Slow down!
500Internal Server Error — We had a problem with our server. Try again later.
502Bad Gateway — We had a problem with our server. Try again later.
503Service Unavailable — We’re temporarily offline for maintenance. Please try again later.