diff --git a/app/templates/views/api-keys.html b/app/templates/views/api-keys.html index 4fa1267c4..e44d5a718 100644 --- a/app/templates/views/api-keys.html +++ b/app/templates/views/api-keys.html @@ -15,25 +15,10 @@
-- To connect to the API you need to create an API Key. -
-- Each service can have multiple API Keys. This allows you to integrate a - number of systems, each with its own key. You can also have separate - keys for your development and test environments. -
- -- API usage is described in - the - developer documentation. -
- {% call(item, row_number) list_table( keys, empty_message="You haven’t created any API keys yet", @@ -55,6 +40,14 @@ {% endif %} {% endcall %} - {{ api_key(current_service.id, "Service ID", thing="service ID") }} ++ API usage is described in the + + API documentation. +
{% endblock %} diff --git a/tests/app/main/views/test_api_keys.py b/tests/app/main/views/test_api_keys.py index 70ad47196..54b4e0378 100644 --- a/tests/app/main/views/test_api_keys.py +++ b/tests/app/main/views/test_api_keys.py @@ -34,7 +34,7 @@ def test_should_show_empty_api_keys_page(app_, assert response.status_code == 200 assert 'You haven’t created any API keys yet' in response.get_data(as_text=True) - assert 'Create new API key' in response.get_data(as_text=True) + assert 'Create an API key' in response.get_data(as_text=True) mock_get_no_api_keys.assert_called_once_with(service_id=service_id)