Skip to Content
Last modified by Admin on 2025/06/27 12:14
From version 6.1
edited by Admin
on 2017/04/05 10:47
Change comment: There is no comment for this version
To version 3.1
edited by sonish
on 2017/04/03 16:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -ONEcount API Documentation
1 +sonish-APIDocument-230317-1008-18
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Admin
1 +XWiki.sonish
Content
... ... @@ -1,8 +1,56 @@
1 +(% class="western" align="center" %)
2 +
3 +
4 +(% class="western" align="center" %)
5 +
6 +
7 +(% class="western" align="center" %)
8 +
9 +
10 +(% class="western" align="center" %)
11 +
12 +
13 +(% class="western" align="center" %)
14 +
15 +
16 +(% class="western" align="center" %)
17 +
18 +
19 +(% class="western" align="center" %)
20 +ONEcount REST API Developer's Guide
21 +
22 +(% class="western" align="center" %)
23 +Version 2.1
24 +
25 +(% class="western" align="center" %)
26 +
27 +
28 +(% class="western" align="center" %)
29 +
30 +
31 +(% class="western" align="center" %)
32 +
33 +
34 +(% class="western" align="center" %)
35 +
36 +
37 +(% class="western" align="center" %)
38 +
39 +
40 +(% class="western" align="center" %)
41 +
42 +
43 +(% class="western" align="center" %)
44 +
45 +
46 +(% class="western" align="center" %)
47 +
48 +
1 1  (% class="western" %)
2 2  **Introduction**
3 3  
4 4  (% class="western" %)
5 -ONEcount REST API is designed to allow you to directly manipulate the underlying data within the ONEcount application. his API can be used to lookup, create and updated different ONEcount resources which are listed below.
53 +ONEcount REST API provides different functionality to accomplish many integration related tasks. This API can be used to lookup, create and updated different ONEcount resources which are listed below.
6 6  
7 7  (% class="western" %)
8 8  REST takes advantage of the HTTP request methods to layer itself into the existing HTTP architecture. These operations consist of the following:
... ... @@ -10,11 +10,14 @@
10 10  1. (((
11 11  (% class="western" %)
12 12  **GET** - Used for lookup of resources
13 -)))
61 +
62 +* (((
14 14  1. (((
15 15  (% class="western" %)
16 16  **PUT** - Used to update a resource
17 17  )))
67 +)))
68 +)))
18 18  1. (((
19 19  (% class="western" %)
20 20  **POST** - Used to create a new resource
... ... @@ -21,56 +21,178 @@
21 21  )))
22 22  
23 23  (% class="western" %)
24 -Specifically, the ONEcount API provides to the following components:
75 +ONEcount API provides following functionalities:
25 25  
26 -1. User data
27 -11. List users
28 -11. Lookup users
29 -11. Create users
30 -11. Update users
31 -1. Transaction data
32 -11. Lookup transactions
33 -11. Create transactions
34 -\\
35 -1. Product data
36 -11. Lookup products
37 -11. Create products
38 -11. Update products
39 -1. Term Data
40 -11. Lookup terms
41 -11. Create terms
42 -11. Update terms
43 -1. Resource Data
44 -11. Lookup resources
45 -11. Create resources
46 -11. Update resources
47 -1. Questions
48 -11. Lookup questions
49 -11. List questions
50 -11. Create questions
51 -1. Source Codes
52 -11. Lookup source code
53 -11. Create source codes
54 -11. Update source codes
55 -1. Attach a resource to a product
56 -1. Leads
57 -11. Create a lead
58 -\\\\\\
77 +1. (((
78 +(% class="western" %)
79 +**Lookup**
59 59  
81 +*
82 +
60 60  (% class="western" %)
61 -**Accessing API**
84 +User lookup
62 62  
86 +*
87 +
63 63  (% class="western" %)
64 -**REST API URL**: [[https:~~/~~/api.onecount.net/v2/>>url:https://api.onecount.net/v2/||shape="rect"]]
89 +Transaction lookup
65 65  
91 +*
92 +
66 66  (% class="western" %)
67 -**Appkey**: THIS WILL BE PROVIDED TO YOU
94 +Question lookup
68 68  
96 +*
97 +
69 69  (% class="western" %)
70 -**
71 -**
99 +Source code lookup
72 72  
101 +*
102 +
73 73  (% class="western" %)
104 +Product lookup
105 +
106 +*
107 +
108 +(% class="western" %)
109 +Term lookup
110 +
111 +*
112 +
113 +(% class="western" %)
114 +Resource lookup
115 +)))
116 +1. (((
117 +(% class="western" %)
118 +**Create**
119 +
120 +*
121 +
122 +(% class="western" %)
123 +Add a user/demo
124 +
125 +*
126 +
127 +(% class="western" %)
128 +Add a question
129 +
130 +*
131 +
132 +(% class="western" %)
133 +Add user transaction
134 +
135 +*
136 +
137 +(% class="western" %)
138 +Add source code
139 +
140 +*
141 +
142 +(% class="western" %)
143 +Add Product
144 +
145 +*
146 +
147 +(% class="western" %)
148 +Add Term
149 +
150 +*
151 +
152 +(% class="western" %)
153 +Add Resource
154 +
155 +*
156 +
157 +(% class="western" %)
158 +Stats – Telemarketing
159 +)))
160 +1. (((
161 +(% class="western" %)
162 +**Update**
163 +
164 +*
165 +
166 +(% class="western" %)
167 +Update a user/demo
168 +
169 +*
170 +
171 +(% class="western" %)
172 +Update a question
173 +
174 +*
175 +
176 +(% class="western" %)
177 +Update source code
178 +
179 +*
180 +
181 +(% class="western" %)
182 +Update product
183 +
184 +*
185 +
186 +(% class="western" %)
187 +Update term
188 +
189 +*
190 +
191 +(% class="western" %)
192 +Update resource
193 +)))
194 +1. (((
195 +(% class="western" %)
196 +**List**
197 +
198 +*
199 +
200 +(% class="western" %)
201 +ListQuestions
202 +
203 +*
204 +
205 +(% class="western" %)
206 +ListSourceCodes
207 +)))
208 +
209 +(% class="western" %)
210 +
211 +
212 +1. (((
213 +(% class="western" %)
214 +**Attach**
215 +)))
216 +
217 +* (((
218 +(% class="western" %)
219 +Attach resource to product
220 +)))
221 +
222 +(% class="western" %)
223 +
224 +
225 +(% class="western" %)
226 +
227 +
228 +(% class="western" %)
229 +**REST API URL**: [[https:~~/~~/api.onecount.net/v2/>>url:https://api.onecount.net/v2/||shape="rect" class="western"]]
230 +
231 +(% class="western" %)
232 +**Appkey**: THIS WILL BE PROVIDED
233 +
234 +(% class="western" %)
235 +
236 +
237 +(% class="western" %)
238 +**Function**
239 +
240 +(% class="western" %)
241 +The ONEcount REST API will be used to create, update & lookup users, transactions and questions e.t.c. in ONEcount hosted install of the client.
242 +
243 +(% class="western" %)
244 +**Accessing API**
245 +
246 +(% class="western" %)
74 74  Your HTTP requests to a REST API resource should contain the following information:
75 75  
76 76  * (((
... ... @@ -91,12 +91,9 @@
91 91  )))
92 92  
93 93  (% class="western" %)
94 -
267 +**Request**
95 95  
96 96  (% class="western" %)
97 -**General API Usage**
98 -
99 -(% class="western" %)
100 100  The request data in POST (for create and update) will consist of request parameters required by each method in JSON format. Value of resource will determine which resource is being requested and the access method will determine whether you are trying to create, update or lookup that resource.
101 101  
102 102  (% class="western" %)
... ... @@ -225,24 +225,42 @@
225 225  
226 226  
227 227  (% class="western" %)
228 -**
229 -**
398 +**Resources**
230 230  
231 231  (% class="western" %)
232 -**
233 -**
401 +Resources are the available entities that can be accessed/modified via API. Each resource can be created, updated or requested by using the corresponding http method described above.
234 234  
403 +* (((
235 235  (% class="western" %)
236 -**
237 -**
238 -
239 -
240 -
405 +questions
406 +)))
407 +* (((
241 241  (% class="western" %)
242 -**RESOURCE: Questions**
409 +users
410 +)))
411 +* (((
412 +(% class="western" %)
413 +products
414 +)))
415 +* (((
416 +(% class="western" %)
417 +terms
418 +)))
419 +* (((
420 +(% class="western" %)
421 +resources
422 +)))
423 +* (((
424 +(% class="western" %)
425 +sources
426 +)))
427 +* (((
428 +(% class="western" %)
429 +transactions
430 +)))
243 243  
244 244  (% class="western" %)
245 -All data fields in ONEcount are made up of questions. Questions are configurable on a per-client basis, and no two customer installations will have the same question (ie., field) layout. Therefore, before querying or updating any ONEcount installation, you'll need to get an understanding of the question layout of the installation. This API segment will allow you to query ONEcount to determine the question layout for the installation. It will also allow you to create new questions within the system. This resource does not allow you to update the data for a specific user (see User section).
433 +**Questions**
246 246  
247 247  (% class="western" %)
248 248  This resource is for manipulating questions resource. Questions in ONEcount means any question that is asked to the subscriber. It could be any questions that appears on customer forms or print forms that gets answered by a subscriber. Questions api call will allow creation, update and search of question in ONEcount. To add a new questions to the system you'll make a POST api call to the questions resource.
... ... @@ -253,7 +253,6 @@
253 253  (% class="western" %)
254 254  There can be 6 types of questions:
255 255  
256 -(% class="wrapped" %)
257 257  |(((
258 258  (% class="western" align="center" %)
259 259  **Type**
... ... @@ -304,7 +304,6 @@
304 304  Checkbox type question. This is a multiple choice, multi response type question. When creating this type of question the choices block also needs to be part of the questions object that will hold the possible choices of the checkbox question.
305 305  )))
306 306  
307 -(% class="wrapped" %)
308 308  |(((
309 309  (% class="western" %)
310 310  **Method**
... ... @@ -377,7 +377,6 @@
377 377  (% class="western" %)
378 378  **GET method can be used to lookup questions.**
379 379  
380 -(% class="wrapped" %)
381 381  |(((
382 382  (% class="western" %)
383 383  **Request**
... ... @@ -408,7 +408,6 @@
408 408  Type: Look up the question type.
409 409  )))
410 410  
411 -(% class="wrapped" %)
412 412  |(((
413 413  (% class="western" %)
414 414  **Response**
... ... @@ -435,7 +435,6 @@
435 435  (% class="western" %)
436 436  **POST method should be used to create questions. The data that is sent should be in JSON format and of type questions as described in references section. Questions object will only need a choices block if the question is a multiple choice question (type=4 or 5 or 6).**
437 437  
438 -(% class="wrapped" %)
439 439  |(((
440 440  (% class="western" %)
441 441  **Request**
... ... @@ -457,7 +457,6 @@
457 457  This defines the question contents and possible responses.
458 458  )))
459 459  
460 -(% class="wrapped" %)
461 461  |(((
462 462  (% class="western" %)
463 463  **Response**
... ... @@ -484,7 +484,6 @@
484 484  (% class="western" %)
485 485  PUT method should be used to update question.
486 486  
487 -(% class="wrapped" %)
488 488  |(((
489 489  (% class="western" %)
490 490  **Request**
... ... @@ -506,7 +506,6 @@
506 506  This defines the question contents and responses.
507 507  )))
508 508  
509 -(% class="wrapped" %)
510 510  |(((
511 511  (% class="western" %)
512 512  **Response**
... ... @@ -589,7 +589,7 @@
589 589  
590 590  (% class="western" %)
591 591  
592 -**RESOURCE: Users**
772 +**Users**
593 593  
594 594  (% class="western" %)
595 595  Users means the customers of your system. Users can be added, updated and searched for using the users resource from the api. For lookup, If a return parameter is specified Users object will have those fields. If nothing is specified by default only UserId is returned.
... ... @@ -612,7 +612,6 @@
612 612  (% class="western" %)
613 613  
614 614  
615 -(% class="wrapped" %)
616 616  |(((
617 617  (% class="western" %)
618 618  **Method**
... ... @@ -732,7 +732,6 @@
732 732  (% class="western" %)
733 733  **GET method should be used to lookup users.**
734 734  
735 -(% class="wrapped" %)
736 736  |(((
737 737  (% class="western" %)
738 738  **Request**
... ... @@ -764,7 +764,6 @@
764 764  
765 765  
766 766  
767 -(% class="wrapped" %)
768 768  |(((
769 769  (% class="western" %)
770 770  **Response**
... ... @@ -791,7 +791,6 @@
791 791  (% class="western" %)
792 792  **POST method should be used to create users.**
793 793  
794 -(% class="wrapped" %)
795 795  |(((
796 796  (% class="western" %)
797 797  **Request**
... ... @@ -843,7 +843,6 @@
843 843  CSV of ONEcount QuestionId's requested back in Users object in response.
844 844  )))
845 845  
846 -(% class="wrapped" %)
847 847  |(((
848 848  (% class="western" %)
849 849  **Response**
... ... @@ -870,7 +870,6 @@
870 870  (% class="western" %)
871 871  **PUT method should be used to update users.**
872 872  
873 -(% class="wrapped" %)
874 874  |(((
875 875  (% class="western" %)
876 876  **Request**
... ... @@ -912,7 +912,6 @@
912 912  RequestDate to use for the demo update. If not provided current date will be used.
913 913  )))
914 914  
915 -(% class="wrapped" %)
916 916  |(((
917 917  (% class="western" %)
918 918  **Response**
... ... @@ -951,7 +951,6 @@
951 951  (% class="western" %)
952 952  This resource is for manipulating products resource. A product can be created, updated or searched.
953 953  
954 -(% class="wrapped" %)
955 955  |(((
956 956  (% class="western" %)
957 957  **Method**
... ... @@ -1037,7 +1037,6 @@
1037 1037  (% class="western" %)
1038 1038  **GET method should be used to lookup products.**
1039 1039  
1040 -(% class="wrapped" %)
1041 1041  |(((
1042 1042  (% class="western" %)
1043 1043  **Request**
... ... @@ -1065,7 +1065,6 @@
1065 1065  Name: Name of the Product for lookup (String)
1066 1066  )))
1067 1067  
1068 -(% class="wrapped" %)
1069 1069  |(((
1070 1070  (% class="western" %)
1071 1071  **Response**
... ... @@ -1092,7 +1092,6 @@
1092 1092  (% class="western" %)
1093 1093  **POST method should be used to create products.**
1094 1094  
1095 -(% class="wrapped" %)
1096 1096  |(((
1097 1097  (% class="western" %)
1098 1098  **Request**
... ... @@ -1120,7 +1120,6 @@
1120 1120  {"Title":"Test123","Description":Testss","Terms":{"Name":"Product123"},"PrimaryFormId":10,"ResourceID":17}
1121 1121  )))
1122 1122  
1123 -(% class="wrapped" %)
1124 1124  |(((
1125 1125  (% class="western" %)
1126 1126  **Response**
... ... @@ -1147,7 +1147,6 @@
1147 1147  (% class="western" %)
1148 1148  PUT method should be used to update an individual product given the product info.
1149 1149  
1150 -(% class="wrapped" %)
1151 1151  |(((
1152 1152  (% class="western" %)
1153 1153  **Request**
... ... @@ -1178,7 +1178,6 @@
1178 1178  {"Title":"Test123","Description":Testss","Terms":{"Name":"Product123"},"PrimaryFormId":10,"ResourceID":17}
1179 1179  )))
1180 1180  
1181 -(% class="wrapped" %)
1182 1182  |(((
1183 1183  (% class="western" %)
1184 1184  **Response**
... ... @@ -1208,7 +1208,6 @@
1208 1208  (% class="western" %)
1209 1209  This resource is for manipulating terms resource. A term can be created, updated or searched.
1210 1210  
1211 -(% class="wrapped" %)
1212 1212  |(((
1213 1213  (% class="western" %)
1214 1214  **Method**
... ... @@ -1265,7 +1265,6 @@
1265 1265  (% class="western" %)
1266 1266  **GET method should be used to lookup products.**
1267 1267  
1268 -(% class="wrapped" %)
1269 1269  |(((
1270 1270  (% class="western" %)
1271 1271  **Request**
... ... @@ -1293,7 +1293,6 @@
1293 1293  Name: Name of the term for lookup (String)
1294 1294  )))
1295 1295  
1296 -(% class="wrapped" %)
1297 1297  |(((
1298 1298  (% class="western" %)
1299 1299  **Response**
... ... @@ -1320,7 +1320,6 @@
1320 1320  (% class="western" %)
1321 1321  **POST method should be used to create products.**
1322 1322  
1323 -(% class="wrapped" %)
1324 1324  |(((
1325 1325  (% class="western" %)
1326 1326  **Request**
... ... @@ -1351,7 +1351,6 @@
1351 1351  {"Name":"Test123","Description":Testss","Duration":10,"ProductId":17}
1352 1352  )))
1353 1353  
1354 -(% class="wrapped" %)
1355 1355  |(((
1356 1356  (% class="western" %)
1357 1357  **Response**
... ... @@ -1378,7 +1378,6 @@
1378 1378  (% class="western" %)
1379 1379  PUT method should be used to update an individual term given the term info.
1380 1380  
1381 -(% class="wrapped" %)
1382 1382  |(((
1383 1383  (% class="western" %)
1384 1384  **Request**
... ... @@ -1409,7 +1409,6 @@
1409 1409  {"Name":"Test123","Description":Testss","Duration":10,"ProductId":17}
1410 1410  )))
1411 1411  
1412 -(% class="wrapped" %)
1413 1413  |(((
1414 1414  (% class="western" %)
1415 1415  **Response**
... ... @@ -1439,7 +1439,6 @@
1439 1439  (% class="western" %)
1440 1440  This resource is for manipulating resources resource. A resource can be created, updated or searched.
1441 1441  
1442 -(% class="wrapped" %)
1443 1443  |(((
1444 1444  (% class="western" %)
1445 1445  **Method**
... ... @@ -1496,7 +1496,6 @@
1496 1496  (% class="western" %)
1497 1497  **GET method should be used to lookup products.**
1498 1498  
1499 -(% class="wrapped" %)
1500 1500  |(((
1501 1501  (% class="western" %)
1502 1502  **Request**
... ... @@ -1524,7 +1524,6 @@
1524 1524  Name: Name of the resource for lookup (String)
1525 1525  )))
1526 1526  
1527 -(% class="wrapped" %)
1528 1528  |(((
1529 1529  (% class="western" %)
1530 1530  **Response**
... ... @@ -1551,7 +1551,6 @@
1551 1551  (% class="western" %)
1552 1552  **POST method should be used to create products.**
1553 1553  
1554 -(% class="wrapped" %)
1555 1555  |(((
1556 1556  (% class="western" %)
1557 1557  **Request**
... ... @@ -1582,7 +1582,6 @@
1582 1582  {"Name":"Test123","Description":Testss","Type":3,"Value":”/digital/”}
1583 1583  )))
1584 1584  
1585 -(% class="wrapped" %)
1586 1586  |(((
1587 1587  (% class="western" %)
1588 1588  **Response**
... ... @@ -1609,7 +1609,6 @@
1609 1609  (% class="western" %)
1610 1610  PUT method should be used to update an individual resource given the resource info.
1611 1611  
1612 -(% class="wrapped" %)
1613 1613  |(((
1614 1614  (% class="western" %)
1615 1615  **Request**
... ... @@ -1640,7 +1640,6 @@
1640 1640  {"Name":"Test123","Description":Testss","Type":3,"Value":”/digital/”}
1641 1641  )))
1642 1642  
1643 -(% class="wrapped" %)
1644 1644  |(((
1645 1645  (% class="western" %)
1646 1646  **Response**
... ... @@ -1665,41 +1665,9 @@
1665 1665  
1666 1666  
1667 1667  (% class="western" %)
1668 -**Resources**
1820 +
1669 1669  
1670 1670  (% class="western" %)
1671 -Resources are the available entities that can be accessed/modified via API. Each resource can be created, updated or requested by using the corresponding http method described above.
1672 -
1673 -* (((
1674 -(% class="western" %)
1675 -questions
1676 -)))
1677 -* (((
1678 -(% class="western" %)
1679 -users
1680 -)))
1681 -* (((
1682 -(% class="western" %)
1683 -products
1684 -)))
1685 -* (((
1686 -(% class="western" %)
1687 -terms
1688 -)))
1689 -* (((
1690 -(% class="western" %)
1691 -resources
1692 -)))
1693 -* (((
1694 -(% class="western" %)
1695 -sources
1696 -)))
1697 -* (((
1698 -(% class="western" %)
1699 -transactions
1700 -)))
1701 -
1702 -(% class="western" %)
1703 1703  
1704 1704  
1705 1705  (% class="western" %)
... ... @@ -1708,7 +1708,6 @@
1708 1708  (% class="western" %)
1709 1709  This resource is for manipulating sources resource. A source can be created, updated or searched.
1710 1710  
1711 -(% class="wrapped" %)
1712 1712  |(((
1713 1713  (% class="western" %)
1714 1714  **Method**
... ... @@ -1765,7 +1765,6 @@
1765 1765  (% class="western" %)
1766 1766  **Sources can be looked up given the code or Id. GET method should be used for lookup.**
1767 1767  
1768 -(% class="wrapped" %)
1769 1769  |(((
1770 1770  (% class="western" %)
1771 1771  **Request**
... ... @@ -1793,7 +1793,6 @@
1793 1793  Source: Source value (String)
1794 1794  )))
1795 1795  
1796 -(% class="wrapped" %)
1797 1797  |(((
1798 1798  (% class="western" %)
1799 1799  **Response**
... ... @@ -1823,7 +1823,6 @@
1823 1823  (% class="western" %)
1824 1824  POST method should be used to create an individual source given the source parameters.
1825 1825  
1826 -(% class="wrapped" %)
1827 1827  |(((
1828 1828  (% class="western" %)
1829 1829  **Request**
... ... @@ -1845,7 +1845,6 @@
1845 1845  Defines the contents that makes up the source. Id parameters should not be set.
1846 1846  )))
1847 1847  
1848 -(% class="wrapped" %)
1849 1849  |(((
1850 1850  (% class="western" %)
1851 1851  **Response**
... ... @@ -1872,7 +1872,6 @@
1872 1872  (% class="western" %)
1873 1873  **PUT method can be used to update an individual source given the id.**
1874 1874  
1875 -(% class="wrapped" %)
1876 1876  |(((
1877 1877  (% class="western" %)
1878 1878  **Request**
... ... @@ -1894,7 +1894,6 @@
1894 1894  Defines the contents that makes up the source. The id parameter needs to be set which will identify the id of the source to be updated.
1895 1895  )))
1896 1896  
1897 -(% class="wrapped" %)
1898 1898  |(((
1899 1899  (% class="western" %)
1900 1900  **Response**
... ... @@ -1927,7 +1927,6 @@
1927 1927  (% class="western" %)
1928 1928  This resource is for manipulating transactions resource. A transaction can be created or searched.
1929 1929  
1930 -(% class="wrapped" %)
1931 1931  |(((
1932 1932  (% class="western" %)
1933 1933  **Method**
... ... @@ -1977,7 +1977,6 @@
1977 1977  (% class="western" %)
1978 1978  Transactions can be looked up using transactionId, date range, userid. Use GET method to do lookup.
1979 1979  
1980 -(% class="wrapped" %)
1981 1981  |(((
1982 1982  (% class="western" %)
1983 1983  **Request**
... ... @@ -2015,7 +2015,6 @@
2015 2015  
2016 2016  
2017 2017  
2018 -(% class="wrapped" %)
2019 2019  |(((
2020 2020  (% class="western" %)
2021 2021  **Response**
... ... @@ -2042,7 +2042,6 @@
2042 2042  (% class="western" %)
2043 2043  POST method can be used to create user transaction. Transaction info needs to be sent as request and a TransactionId will be returned when the transaction is created.
2044 2044  
2045 -(% class="wrapped" %)
2046 2046  |(((
2047 2047  (% class="western" %)
2048 2048  **Request**
... ... @@ -2064,7 +2064,6 @@
2064 2064  Contains fields that define a transaction. Id field should not be set.
2065 2065  )))
2066 2066  
2067 -(% class="wrapped" %)
2068 2068  |(((
2069 2069  (% class="western" %)
2070 2070  **Response**
... ... @@ -2088,14 +2088,6 @@
2088 2088  
2089 2089  
2090 2090  
2091 -
2092 -
2093 -
2094 -
2095 -
2096 -
2097 -
2098 -
2099 2099  (% class="western" %)
2100 2100  **Stats**
2101 2101  
... ... @@ -2124,7 +2124,6 @@
2124 2124  
2125 2125  This resource is for manipulating telemarketing stat resource. A telemarketing stat can be created or listed.
2126 2126  
2127 -(% class="wrapped" %)
2128 2128  |(((
2129 2129  (% class="western" %)
2130 2130  **Method**
... ... @@ -2171,7 +2171,6 @@
2171 2171  (% class="western" %)
2172 2172  POST method can be used to create telemarketing stat. Telemarketing info needs to be sent as request and an Id will be returned when the transaction is created.
2173 2173  
2174 -(% class="wrapped" %)
2175 2175  |(((
2176 2176  (% class="western" %)
2177 2177  **Request**
... ... @@ -2245,7 +2245,6 @@
2245 2245  
2246 2246  )))
2247 2247  
2248 -(% class="wrapped" %)
2249 2249  |(((
2250 2250  (% class="western" %)
2251 2251  **Response**
... ... @@ -2269,14 +2269,6 @@
2269 2269  
2270 2270  
2271 2271  
2272 -
2273 -
2274 -
2275 -
2276 -
2277 -
2278 -
2279 -
2280 2280  (% class="western" %)
2281 2281  **Reference**
2282 2282  
... ... @@ -2283,7 +2283,6 @@
2283 2283  (% class="western" %)
2284 2284  **Type: Questions**
2285 2285  
2286 -(% class="wrapped" %)
2287 2287  |(((
2288 2288  (% class="western" %)
2289 2289  **Property Name**
... ... @@ -2363,7 +2363,6 @@
2363 2363  (% class="western" %)
2364 2364  **Type: Choices**
2365 2365  
2366 -(% class="wrapped" %)
2367 2367  |(((
2368 2368  (% class="western" %)
2369 2369  **Property Name**
... ... @@ -2430,7 +2430,6 @@
2430 2430  (% class="western" %)
2431 2431  **Type: Users**
2432 2432  
2433 -(% class="wrapped" %)
2434 2434  |(((
2435 2435  (% class="western" %)
2436 2436  **Property Name**
... ... @@ -2487,7 +2487,6 @@
2487 2487  (% class="western" %)
2488 2488  **Type: Demo**
2489 2489  
2490 -(% class="wrapped" %)
2491 2491  |(((
2492 2492  (% class="western" %)
2493 2493  **Property Name**
... ... @@ -2534,7 +2534,6 @@
2534 2534  (% class="western" %)
2535 2535  **Type: Transactions**
2536 2536  
2537 -(% class="wrapped" %)
2538 2538  |(((
2539 2539  (% class="western" %)
2540 2540  **Property Name**
... ... @@ -2681,7 +2681,6 @@
2681 2681  (% class="western" %)
2682 2682  **Type: Sources**
2683 2683  
2684 -(% class="wrapped" %)
2685 2685  |(((
2686 2686  (% class="western" %)
2687 2687  **Property Name**
... ... @@ -2741,7 +2741,6 @@
2741 2741  (% class="western" %)
2742 2742  **Type: Products**
2743 2743  
2744 -(% class="wrapped" %)
2745 2745  |(((
2746 2746  (% class="western" %)
2747 2747  **Property Name**
... ... @@ -2798,7 +2798,6 @@
2798 2798  (% class="western" %)
2799 2799  **Type: Terms**
2800 2800  
2801 -(% class="wrapped" %)
2802 2802  |(((
2803 2803  (% class="western" %)
2804 2804  **Property Name**
... ... @@ -2885,7 +2885,6 @@
2885 2885  (% class="western" %)
2886 2886  **Type: Resources**
2887 2887  
2888 -(% class="wrapped" %)
2889 2889  |(((
2890 2890  (% class="western" %)
2891 2891  **Property Name**
... ... @@ -2983,7 +2983,6 @@
2983 2983  (% class="western" %)
2984 2984  **Type: Telemarketing**
2985 2985  
2986 -(% class="wrapped" %)
2987 2987  |(((
2988 2988  (% class="western" %)
2989 2989  **Property Name**
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -3539009
1 +3538998
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/3539009/ONEcount API Documentation
1 +https://info.onecount.net//wiki/spaces/OD/pages/3538998/sonish-APIDocument-230317-1008-18