I’ve recently completed onboarding and moved my product into production with a set of APIs.
I’m now developing the next version of the same product, which requires access to additional APIs.
Should I create a new product in the onboarding service for this, or can I add the additional APIs to my existing product and complete onboarding for those APIs only?
Hi Stuart,
Thanks for using the community.
There are two products that can be added to applications: one for healthcare worker access and one that is work‑application‑restricted. These should be set up as distinct products, so if you require both, you should have two separate applications. I appreciate this isn’t directly answering your question, but it’s useful context in case the new approach moves in that direction.
In terms of the new interactions you may be referring to, these are tied to the ASID. If you’re happy with your existing setup in INT (and assuming the application structure aligns with the point above), there’s no action needed — in INT we allow access to all endpoints.
For production, you would follow the same assurance process you originally went through. If production applications need to be upgraded, we would raise a request to update the ASIDs already associated with your production apps. In PROD, access is limited strictly to the permissions you’ve been assured for.
The production and assurance process is explained in more detail here:
https://digital.nhs.uk/services/e-referral-service/api/integration-process/stage-5-maintain
Hope that helps, but let me know if you need anything clarified.