Advertisement
Guest User

Untitled

a guest
Sep 13th, 2017
96
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.84 KB | None | 0 0
  1. <br>
  2.  
  3. ### GET /claims
  4. _Response: Array of claims objects_
  5. ```
  6. [
  7. {
  8. id: 7498923432,
  9. date: 'June 10, 2016', (or whatever format)
  10. amount: 430.00, (or whatever format)
  11. memberName: 'John Smith', (cna be fname and lname too, whatever is easier)
  12. healthplan: 'BCBS FL',
  13. status: true, (this is just for "Paid' or "Not Paid"... not sure if there is other status's, if there is just send back the status string I guess)
  14. provider: 'Dr. Davis',
  15. }
  16. ]
  17. ```
  18. <hr>
  19.  
  20. ### GET /claims/:id
  21. I do not need this endpoint if you can give me all the info in GET /claims, it is not alot so we can maybe get away with just the list
  22.  
  23. <hr>
  24.  
  25. ### GET /contacts/poa
  26. _ResponseE: Array of objects of Power of Attorney contacts_
  27. ```
  28. [
  29. {
  30. fName: 'John',
  31. lName: 'Morgan',
  32. relationship: 'Attorney',
  33. phone: '3335679894',
  34. address: '20 N Orange Ave Suite 1600 Orlando FL 32801',
  35. email: 'john@morgan.com'
  36. }
  37. ]
  38. ```
  39.  
  40. <hr>
  41.  
  42. ### GET /contacts/providers
  43. _Response: Array of objects of provider contacts_
  44. ```
  45. [
  46. {
  47. address: '4539 S Dale Mabry Hwy #110, Tampa, FL 33611',
  48. phone: '5557672334',
  49. fName: 'Dr. Christopher',
  50. lName: 'Davis',
  51. title: 'Advanced Rehabilitation'
  52. }
  53. ]
  54. ```
  55.  
  56. <hr>
  57.  
  58. ### GET /coverage/plan
  59. _Response_
  60. ```
  61. {
  62. plan: 'Blue Cross PPO',
  63. type: 'Medi-Cal',
  64. effectiveDate: '1/1/2017', (whatever format)
  65. termDate: '12/31/2017', (whatever format)
  66. }
  67. ```
  68.  
  69. <hr>
  70.  
  71. ### GET /coverage/primarycare
  72. _Response_
  73. ```
  74. {
  75. fName: 'Robert',
  76. lName: 'Johnson',
  77. address: '3006 W Azeele St, Tampa, FL 33609',
  78. phone: '5551230987'
  79. }
  80. ```
  81.  
  82. <hr>
  83.  
  84. ### GET /directory/specialties
  85. _Response: Array of objects of specialties_
  86. ```
  87. [
  88. {
  89. name: 'Acupuncture',
  90. id: 1
  91. },
  92. {
  93. name: 'Orthopedic',
  94. id: 2
  95. }
  96. ]
  97. ```
  98.  
  99. <hr>
  100.  
  101. ### POST /directory/search
  102. Not 100% how the search should work
  103.  
  104. _Request: something like (only going to require that at least 1 field is set):_
  105. ```
  106. {
  107. fName: 'Bob',
  108. lName: 'Smith',
  109. practiceName: 'Docs R Us',
  110. state: 'FL',
  111. zip: '33123',
  112. specialty: '5' (I will be sending back to you the 'id' number from the specialties from /directory/specialties)
  113. }
  114. ```
  115. _Response: array of objects_
  116. ```
  117. [
  118. {
  119. title: 'Orthopaedic Medical Group of Tampa Bay',
  120. address: '4541 S Dale Mabry Hwy, Tampa, FL 33611',
  121. phone: 18135559986,
  122. other: ['Orthopedic, Surgery'] <-- array of the practice's specialties
  123. }
  124. ]
  125. ```
  126.  
  127. <hr>
  128.  
  129. ### GET /deductible
  130. _Response_
  131. ```
  132. {
  133. max: 5000,
  134. current: 1200,
  135. totalClaims: 12 <-- not sure if this belongs or not, this is just the total claims, I imagine you can get this when you are totalling the current amount the user has spent towards the deductible
  136. }
  137. ```
  138.  
  139. <hr>
  140.  
  141. ### GET /idcards
  142. _Response_
  143. ```
  144. {
  145. name: 'John Smith', <-- can be fName, lName, etc, this is just whoevers name is on the card I guess?
  146. cardID: 'ZXY42343423423234',
  147. groupID: '99',
  148. coverageDate: '1/1/2017' (whatever format)
  149. }
  150. ```
  151.  
  152. <hr>
  153.  
  154. ### GET /user (gets the currently auth'd user)
  155.  
  156. This is pretty basic, maybe we should send in more info about the user? Like addresses and stuff?
  157.  
  158. _Response_
  159. ```
  160. {
  161. fName: 'Bob;,
  162. lName: 'Smith',
  163. memberId: '213ZXYABC1234'
  164. }
  165. ```
  166.  
  167. <hr>
  168.  
  169. ### POST /user/register
  170. _Request:_
  171. ```
  172. {
  173. memberId: '123456789',
  174. fName: 'Bob',
  175. lName: 'Smith',
  176. userId: '123' <-- I have no idea what this is, it was in the old app
  177. email: 'bob@bob.com',
  178. password: 'password'
  179. }
  180. ```
  181. _Response_
  182. ```
  183. {
  184. result: 'success'
  185. }
  186. ```
  187.  
  188. <hr>
  189.  
  190. ### POST /user/changepass
  191. _Request:_
  192. ```
  193. {
  194. current: 'currentPassword',
  195. new: 'newPassword'
  196. }
  197. ```
  198. _Response_
  199. ```
  200. {
  201. result: 'success'
  202. }
  203. ```
  204.  
  205. ### POST /user/forgotpass
  206. _Request:_
  207. ```
  208. {
  209. email: 'bob@bob.com'
  210. }
  211. ```
  212. _Response_
  213. ```
  214. {
  215. result: 'success'
  216. }
  217. ```
  218. **In the password email, please send them to /guest/forgotpass?token=whatever**
  219.  
  220. <hr>
  221.  
  222.  
  223. ### POST /user/forgotpass/change
  224. This is for the password reset via email, you will send them a link to **/guest/forgotpass?token=whatever**
  225.  
  226. _Request:_
  227. ```
  228. {
  229. new: 'password',
  230. token: 'sometoken'
  231. }
  232. ```
  233. _Response_
  234. ```
  235. {
  236. result: 'success'
  237. }
  238. ```
  239.  
  240. <hr>
  241.  
  242. ### POST /user/login
  243. _Request:_
  244. ```
  245. {
  246. user: 'user@email.com',
  247. pass: 'password',
  248. client_id: 'clientSecret',
  249. grant_type: 'token'
  250. }
  251. ```
  252. _Response_
  253. ```
  254. {
  255. token: 'somelongtoken',
  256. refreshToken: 'someotherlongtoken',
  257. }
  258. ```
  259.  
  260. <hr>
  261.  
  262. ### POST /user/refresh
  263. For refreshing tokens
  264.  
  265. _Request:_
  266. ```
  267. {
  268. client_id: 'clientSecret',
  269. grant_type: 'refresh',
  270. refreshToken: 'somelongtoken'
  271. }
  272. ```
  273. _Response_
  274. ```
  275. {
  276. token: 'somelongtoken',
  277. refreshToken: 'someotherlongtoken',
  278. }
  279. ```
  280.  
  281. <hr>
  282.  
  283. ### POST /user/logout
  284. I will send you the current tokens so you can invalidate them
  285.  
  286. _Request:_
  287. ```
  288. {
  289. token: 'somelongtoken',
  290. refreshToken: 'someotherlongtoken',
  291. client_id: 'clientSecret'
  292. }
  293. ```
  294. _Response_
  295. ```
  296. {
  297. result: 'success'
  298. }
  299. ```
  300. <hr>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement