Broken link to "Submit non-functional requirements" on MESH API catelogue

Message Exchange for Social Care and Health (MESH)
1

On https://digital.nhs.uk/developer/api-catalogue/message-exchange-for-social-care-and-health-api the next step after “Develop and test” is listed as “Sign in to the digital onboarding to answer questions on ‘non-functional’ requirements” which links to hXXps://identity.prod.api.platform.nhs.uk/auth/realms/developer-identity/login-actions/authenticate?client_id=digital-onboarding-service&tab_id=YTe9EqJeUCc

When I click this, the page just says “FORBIDDEN”.

I’ve tried in FireFox and Chrome. Private modes as well.

How can I progress our application ?

2

Hi there,

Sorry you’ve experienced issues logging into digital onboarding service (DOS) via the MESH API catalogue page. The link you’ve highlighted is incorrect and will be update. In the meantime, you can log into DOS and start/add to/complete your MESH application here:

https://onboarding.prod.api.platform.nhs.uk/

Kind Regards
MESH team

3

Oh, thanks.

Am I doing it wrong ? I search for “message” under " APIs available in this environment " and nothing is returned apart from “Communications Manager” ? Same for “MESH”

4

Hi again,

Do you currently have a MESH application in progress? If not, then these are the steps to initiate one:

  1. Log into the the onboarding portal (https://onboarding.prod.api.platform.nhs.uk/)
  2. You will see three options; Environment Access, Product onboarding, Developer community. Choose Product onboarding
  3. You will now see any applications you currenlty have and a button labelled ‘Add Product’. If you don’t currently have a MESH application, click on the ‘Add Product’ button.
  4. You can now give you application a product name, and select the MESH API. This will create your application where you can then answer the needed questions.

Hope the above helps

Regards
MESH team

5

I think so ? “Application ID 4dbedd44-1ed3-4a1d-a490-7c418ad1802e” was created a year ago (sorry for the delay!) and we’ve been allocated MESH inboxes and API certificates in the integration testing environment that seem to be (now :slight_smile: ) working well.

We have Spine PDS integrations running in live, so already have a completed “product” page with all the connection agreements etc signed and passed.

Feel free to email or DM me if it’s easier to sort things out that way.

6

OK, cool. So, do you have anything under the ‘Environment Access’ section of your developer account?

  1. Log into the the onboarding portal
  2. You will see three options; Environment Access, Product onboarding, Developer community. Environment Access

Did you originally setup the developer account?

I’ll do a bit of digging on this side with the app ID you’ve provided, too.

7

Hi,

Yup, so under “Environment access” we have 3 items, one for PDS int., one for PDS live, and one for MESH live, based on the names and the “connected APIs” listed against the other two.

I’m not sure if me or my colleague would have set up the account at the very start several years ago, but under “My Teams” it lists our company and “role” is “owner”.

8

Thanks,

I think it’s probably best to log a service ticket for us to look into this further. Please can you Contact the National Service Desk (NSD) by calling 0300 303 5035 or by emailing ssd.nationalservicedesk@nhs.net.

We can then take a deeper look into the developed account and what’s enabled on it.

Regards
Mesh Team