System Requirements -
Windows 98 SE, ME, 2000, XP, Windows7, Windows8, UNIX, Linux or MacOS operating system. -
Internet Explorer 6 SP1 (for Windows platform) -
cURL library (for developers using PHP)
Error Codes Error Code | Description | 01 | Incorrect User Name
Incorrect Password
Incorrect Dealer Code
| 02 | Message Sending: Insufficient balance
Invalid ID: No such message (ID) code
Reporting: Package not processed or awaiting at the Gateway side | 03 | Undefined Action parameter | 04 | No XML received | 05 | Missing or incorrect XML node | 06 | Undefined Originator information | 07 | Missing Message Code (ID) | 08 | No SMS sent between the specified dates | 09 | Empty or incorrect date fields | 10 | SMS could not be sent | 11 | Undefined error | 12 | Unauthorized access attempt | 13 | User requested for reporting does not exist |
Error Code Return Formats
XML *<*mobiltim*>*
*<*status*>*00*<*/status*>*
*<*description*>*success*<*/description*>*
*<*/mobiltim*>*
JSON
{
"mobiltim": {
"status": "00",
"description":"success"
}
}
Querying
TR ID Numbers, of which MSISDN information will be queried, must be prepared as per the XML / JSON formats quoted below and must be sent to Gateway. The Gateway creates single ID information for each query. With this ID information you can prepare the query results.
XML *<*?xml version="1.0" encoding="UTF-8"?*>*
*<*mobiltim*>*
*<*username*>*username*<*/username*>*
*<*companycode*>*companycode*<*/companycode*>*
*<*password*>*password*<*/password*>*
*<*action*>*1*<*/action*>*
*<*tr id nolist*>*
*<*tr id no*>*12345678901*<*/tr id no*>*
*<*tr id no*>*12345678902*<*/tr id no*>*
*<*tr id no*>*12345678903*<*/tr id no*>*
*<*/tr id nolist*>*
*<*description*>**<*/description*>*
*<*/mobiltim*>*
JSON
{
"mobiltim": {
"username": "username",
"companycode": "companycode",
"password": "password",
"action": "1",
"tr id nolist": {
"tr id no": [
"12345678901",
"12345678902",
"12345678903"
]
},
"description" : "description"
}
}
Node | Data Type | Description | Username | String | User name assigned by Mobildev | Companycode | String | Dealer code | Password | String | Password information associated with your user account | Action | İnt | Default defined process ID for the query method defined at the Gateway | TR ID Nolist | List | The list of TR ID No to query | TR ID No | String | 11 digit TR ID No | Description | String | Description field related to the query |
Once you post the XML / JSON statement you created to the Gateway;
1) If the operation is successful
XML
*<*mobiltim*>*
*<*status*>*0*<*/status*>*
*<*requestId*>*requestId*<*/requestId*>*
*<*/mobiltim*>*
JSON
{
"mobiltim": {
"status": "0",
"requestId": "requestId"
}
}
Process Id belonging to the query request sent is the requestId. Data format: Int
2) If the operation fails, please refer to Error Codes
Reporting The queries you have made may differ according to the number of TR ID No you sent. It is recommended to wait for querying to finish for proceeding with database recording process.
To get the reports for the previously made queries:
XML *<*?xml version="1.0" encoding="UTF-8"?*>*
*<*mobiltim*>*
*<*username*>*username*<*/username*>*
*<*companycode*>*companycode*<*/companycode*>*
*<*password*>*password*<*/password*>*
*<*action*>*2*<*/action*>*
*<*packetId*>*requestId*<*/packetId*>*
*<*/mobiltim*>*
JSON
{
"mobiltim": {
"username":"username",
"companycode":"companycode",
"password":"asdf1234",
"action": "2",
"packetId":"requestId"
}
}
Once you prepare the statement appropriate for your integration and post it to the Gateway;
Node | Data Type | Description | Username | String | User name assigned by Mobildev | Companycode | String | Dealer code | Password | String | Password information associated with your user account | Action | İnt | Default defined process ID for the query method defined at the Gateway | packetId | Int | RequestId information belonging to the query you made previously. |
1) If the operation is successful
XML
*<*?xml version="1.0" encoding="UTF-8" ?*>*
*<*mobiltim*>*
*<*status*>*0*<*/status*>*
*<*packetId*>*3*<*/packetId*>*
*<*senddate*>*2012-11-02 09:42:10*<*/senddate*>*
*<*packetStatus*>*1*<*/packetStatus*>*
*<*endDate*>*2012-11-02 10:05:46*<*/endDate*>*
*<*recordCount*>*3*<*/recordCount*>*
*<*tr id nolist*>*
*<*tr id no*>*
*<*value*>*12345678901*<*/value*>*
*<*search-result*>*2*<*/search-result*>*
*<*/tr id no*>*
*<*tr id no*>*
*<*value*>*12345678902*<*/value*>*
*<*search-result*>*1*<*/search-result*>*
*<*/tr id no*>*
*<*tr id no*>*
*<*value*>*12345678903*<*/value*>*
*<*search-result*>*0*<*/search-result*>*
*<*msisdn-list*>*
*<*msisdn*>*532XXXXXX*<*/msisdn*>*
*<*msisdn*>*533XXXXXX*<*/msisdn*>*
*<*/msisdn-list*>*
*<*/tr id no*>*
*<*/tr id nolist*>*
*<*/mobiltim*>*
Node | Type | Description | Status | İnt | Operation successful code for a successful query | packetId | İnt | requestId information for the report | Senddate | Date | Query start date, data format: yyyy-mm-dd hh:mm:ss | Packetstatus | Int | Query status;
0 – Awaiting query
1 - Query Completed
6 - Cancelled due to undefined user or incorrect content
7 - System error
9 - Processing Query | Enddate | Date | Query end date, data format: yyyy-mm-dd hh:mm:ss | RecordCount | Int | Number of records in the packet queried | TR ID Nolist | List*<*TR ID No*>* | List belonging to the TR ID numbers queried | TR ID No | Xml / json node | | value | String | TR ID Information | search-result | İnt | Query Result for the related T.R. ID information:
0 - Query successful
1 - T.R. ID no is not defined in the system, it is not being serviced by Turkcell.
2 - For the queried T.R. ID no, there is no registered line within Turkcell system -with phone book registration permission-. Other values returned as the query result are system errors. | msisdn-list | List*<*msisdn*>* | If the query result is successful, this is the GSM No information advised by Turkcell. | msisdn | String | msisdn belonging to the TR ID no |
2) If the operation fails, please refer to Error Codes
| 
