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
Copy file name to clipboardExpand all lines: docs/collections/_consumers/getting-started.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ If you have installed the local repository requirements or are utilising the dev
30
30
31
31
## Documentation
32
32
33
-
This documentation is maintained within the [/docs](/docs) folder of the repository and published to [GitHub pages](https://nhsdigital.github.io/nhs-notify-supplier-api/) on PR merge
33
+
This documentation is maintained within the [/docs](https://github.com/NHSDigital/nhs-notify-supplier-api/tree/main/docs) folder of the repository and published to [GitHub pages](https://nhsdigital.github.io/nhs-notify-supplier-api/) on PR merge
34
34
35
35
## SDK Assets
36
36
@@ -54,7 +54,7 @@ It will provide limited, fixed responses and does not require authentication to
54
54
55
55
There are two ways to access the sandbox:
56
56
57
-
- The public sandbox [https://sandbox.api.service.nhs.uk/notify-supplier](https://sandbox.api.service.nhs.uk/notify-supplier)
57
+
- The public sandbox [https://sandbox.api.service.nhs.uk/notify-supplier](https://sandbox.api.service.nhs.uk/nhs-notify-supplier)
58
58
- Local Build
59
59
60
60
You can build the sandbox locally by installing the repository requirements (or using the devcontainer) and running:
Copy file name to clipboardExpand all lines: docs/collections/_consumers/integration.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ You have 90 calendar days to complete onboarding activities and submit all requi
34
34
35
35
---
36
36
37
-
## Pre-onboarding & Conformance
37
+
## Pre-onboarding and Conformance
38
38
39
39
Before you can begin technical onboarding, your organisation must:
40
40
@@ -59,10 +59,8 @@ This triggers an event to make the letter available for you to retrieve.
59
59
### List of letters and downloads
60
60
61
61
Retrieve a list of all available letters, including key details such as the letter ID and current status.
62
-
The list only contains the summary information - not the actual PDF files.
63
-
To access each full letter, download the PDF directly by making a request to the `/letters/{id}/data` endpoint.
64
-
This will redirect to a short-lived URL to download the file.
65
-
These links are temporary and expire after about one minute, so downloads should be completed right away or re-requested if the link has expired.
62
+
The list only contains the summary information — not the actual PDF files.
63
+
To access each full letter, download the PDF directly by making a request to the /the GET letters/{id}/data endpoint. This will redirect to a short-lived URL to download the file. These links are temporary and expire after about one minute, so downloads should be completed right away or re-requested if the link has expired.
66
64
67
65
### API access
68
66
@@ -121,7 +119,6 @@ Refer to the Letter Status Lifecycle diagram below for the complete sequence of
121
119
## Prepare your integration
122
120
123
121
You must prepare your integration before you can get access to the NHS Notify integration environment.
124
-
You’ll need technical or developer support to complete tasks in this step.
125
122
126
123
### To set up your APIM application
127
124
@@ -146,7 +143,7 @@ How you build your integration to meet your needs is your responsibility.
146
143
147
144
The API is defined using the [OpenAPI Specification (OAS)](https://spec.openapis.org/oas/latest.html) format.
148
145
149
-
You can find it on [GitHub](https://github.com/NHSDigital/nhs-notify-supplier-api/tree/main/specification/api) and on the [NHS England Developer Catalogue](https://digital.nhs.uk/developer/api-catalogue/Alphabet/N).
146
+
You can find it on [GitHub](https://github.com/NHSDigital/nhs-notify-supplier-api/tree/main/specification/api) and on the [NHS API Catalogue](https://digital.nhs.uk/developer/api-catalogue/nhs-notify-supplier).
150
147
151
148
A Postman collection will also be available in [GitHub](https://github.com/NHSDigital/nhs-notify-supplier-api/tree/main/postman) to explore the requests within the API.
152
149
@@ -206,7 +203,9 @@ You’ll need to submit both digital proofs (for content and layout verification
206
203
207
204
Only once your proofs have been reviewed and approved will you receive confirmation that your system and outputs are ready to move forward into the live (production) environment.
208
205
209
-
Digital proof will need to be sent via e-mail using this address: <[email protected]> and physical proof will need to be sent to: Mr Wayne Shirt (NHS Notify), 6th Floor, 7 & 8 Wellington Place, Leeds, West Yorkshire, LS1 4AP.
206
+
Digital proof will need to be sent via e-mail using this address: <[email protected]> and physical proof will need to be sent to:
207
+
208
+
Mr Wayne Shirt (NHS Notify), 6th Floor, 7 & 8 Wellington Place, Leeds, West Yorkshire, LS1 4AP.
0 commit comments