5 Commits

Author	SHA1	Message	Date
Alexey Bezhan	acfe8092fc	Add route secret key header to the API requests ... Currently requests to the API made from the admin app are going from PaaS admin app to the nginx router ELB, which then routes them back to the api app on PaaS. This makes sense for external requests, but for requests made from the admin app we could skip nginx and go directly to the api PaaS host, which should reduce load on the nginx instances and potentially reduce latency of the api requests. API apps on PaaS are checking the X-Custom-Forwarder header (which is set by nginx on proxy_pass requests) to only allow requests going through the proxy. This adds the custom header to the API client requests, so that they can pass that header check without going through nginx.	2018-02-28 11:28:46 +00:00
venusbb	1ab4681ff5	Use the revise api endpoints without current-year parameter	2017-11-09 13:18:09 +00:00
venusbb	8ea38ba7b6	Use annual_billing tables at backend for getting and updating free_sms_fragment_limit	2017-10-31 11:22:57 +00:00
Imdad Ahad	232912ab3b	Call the correct endpoint to retrieve yearly billing usage	2017-08-17 16:02:30 +01:00
Imdad Ahad	32242c4501	Update the usage page to use new billing endpoints ... * Create new billing_api_client for separation and remove older methods in the service_api_client	2017-08-16 16:31:47 +01:00