Leo Hemsted 78a6f86043 use service statistics endpoint instead of detailed service ...

we're not actually looking at the detailed service aspects - just
the stats. We're doing this in three places:

* dashboard
* notification activity page
* when checking jobs to see if we're over the daily limit

change these places to use a new api endpoint (service/id/statistics),
which hopefully be a little more performant, and will definitely be a
little more organised - moving away from generic endpoints with loads
of optional parameters.

We still need the detailed endpoints for the platform admin page tho.

Depends on https://github.com/alphagov/notifications-api/pull/1865

2018-05-09 14:00:24 +01:00

..

__init__.py

…

test_billing_client.py

…

test_email_branding_client.py

Change organisations to email branding

2018-02-07 17:41:23 +00:00

test_events_client.py

…

test_invite_client.py

remove all instances of db style permissions

2018-03-06 13:08:06 +00:00

test_job_client.py

Stop posting job metadata to the API

2018-05-01 09:47:04 +01:00

test_notification_client.py

define isort first party (app and tests)

2018-04-25 14:12:58 +01:00

test_notify_admin_api_client.py

define isort first party (app and tests)

2018-04-25 14:12:58 +01:00

test_service_api_client.py

use service statistics endpoint instead of detailed service

2018-05-09 14:00:24 +01:00

test_template_statistics_client.py

fix imports

2018-03-06 13:10:37 +00:00

test_user_client.py

Merge pull request #2034 from alphagov/zendesk

2018-04-27 14:33:31 +01:00