Skip to content

Commit 9b1f8fb

Browse files
authored
Merge pull request #101 from NHSDigital/mm-mesh-1116-api-versioning
mesh-1116: remove initial api versioning callout
2 parents 5aa0805 + f0fd7e8 commit 9b1f8fb

1 file changed

Lines changed: 3 additions & 6 deletions

File tree

specification/mesh-api.yaml

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -52,10 +52,6 @@ info:
5252
5353
You can do some things while you wait, but expect the end-to-end integration process to take 1 month or more.
5454
55-
### Versioning
56-
57-
MESH API now has BETA support for versioning on certain endpoints in order to allow us to safely make new features and capabilities available to API consumers. For information on how to call a versioned API endpoint see [API Versioning](#api-description__api-versioning).
58-
5955
### Get started
6056
6157
To get started, sign in or create a developer account for digital onboarding, complete the 'Setup and eligibility' section and submit it.
@@ -234,9 +230,10 @@ info:
234230
235231
This sandbox can be used for local development and currently does not require a client certificate
236232
237-
238233
## API Versioning
239-
234+
235+
MESH API now has `live-beta` support for versioning on certain endpoints in order to allow us to safely make new features and capabilities available to API consumers.
236+
240237
MESH uses the `Accept` header to support different versions in the same API, sending a different `Accept` header will vary the response, refer to individual API endpoints for more detail.
241238
242239
If not specified `Accept: application/json` will be assumed and the lowest supported response version for that particular endpoint will be returned.

0 commit comments

Comments
 (0)