You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Feel free to add content and custom Front Matter to this file.
3
+
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
4
+
5
+
layout: page
6
+
title: API
7
+
parent: Features
8
+
nav_order: 1
9
+
permalink: /features/api
10
+
section: Accessing NHS Notify
11
+
---
12
+
13
+
NHS England organisations and services can integrate the NHS Notify API with their web applications or back office systems.
14
+
15
+
[Read our API documentation (opens in a new tab)](https://digital.nhs.uk/developer/api-catalogue/nhs-notify){:target="\_blank"}.
16
+
17
+
If you’re a developer you can also try our [sandbox test environment (opens in a new tab)](https://digital.nhs.uk/developer/api-catalogue/nhs-notify#overview--environments-and-testing){:target="\_blank"}.
# Feel free to add content and custom Front Matter to this file.
3
+
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
4
+
5
+
layout: page
6
+
title: MESH
7
+
parent: Features
8
+
nav_order: 2
9
+
permalink: /features/mesh
10
+
section: Accessing NHS Notify
11
+
---
12
+
13
+
NHS England organisations and services can use the [Message Exchange for Social Care and Health (MESH)](https://digital.nhs.uk/services/message-exchange-for-social-care-and-health-mesh){:target="\_blank"} to send messages with NHS Notify.
14
+
15
+
You should only use MESH to send messages if your organisation or service:
16
+
17
+
- has limited developer or technical capacity
18
+
- only needs to send batches of messages to specific groups of recipients
19
+
- does not need advanced features offered by NHS Notify API
20
+
21
+
[Read our MESH documentation (opens in a new tab)](https://digital.nhs.uk/developer/api-catalogue/nhs-notify-mesh){:target="\_blank"}.
22
+
23
+
Check if MESH is right for you by contacting our engagement team at <[email protected]>.
0 commit comments