Accessing Multiple Partner APIs on the Same Server

API Platform
, , ,
1

Hi all,

I currently have Partner API access for two practices, and I’m trying to integrate both on the same server/system.

I’ve successfully activated the API for the first practice — everything is working as expected. However, when I attempt to activate the second practice, it doesn’t activate my product and instead keeps prompting for the username and password repeatedly.

Has anyone encountered this issue before? Is it possible to activate and use partner APIs for multiple practices in the same environment? Any guidance or suggestions would be greatly appreciated. @navin.bose

Thanks!

2

Hi Ali,

Thank you for getting in touch with NHS England API Platform team.

Yes, it is possible to access Partner APIs for multiple practices on the same server, but repeated login prompts usually happen due to shared config or session collisions.

You could explore the following options to resolve the issue:

  • Ensure each practice has a separate Product ID and activation.
  • Use isolated config directories per practice (credentials, registry keys, etc.).
  • Optionally, run separate Windows services per integration to prevent session conflicts.
  • Confirm both practices are fully activated in EMIS Web and mapped to your product.

If the issue persists, EMIS Partner Support can check logs for any activation issues.
Contact EMIS Support or Consult the Partner API Forum

  • If you have tried the above steps and still can’t edit the consultation, EMIS Partner Support may be able to offer more specific guidance. Provide them with detailed logs, the exact endpoints and payload you are using, and any API error responses you receive.

Hope the above helps.

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API specific queries, please reach out the relevant API teams.

3

Thank you for your response.

I’ve successfully activated the first practice. However, when I try to activate the second one, it keeps prompting me to activate again, even though I’m entering the correct credentials.

One more thing i have same productID/supplierID for both of our practices

image
image611×431 29.2 KB

4

Hi Ali,

From the EMIS documentation and developer community experience, this issue is likely caused by session or registry conflict, especially when:

  • The same Product ID is reused across practices without isolating environment/session data.
  • The Partner API activation is not correctly scoped or cleared between attempts.
  • The EMIS registry keys hold a cached session for the first practice and doesn’t support reactivation under a second context on the same product.

As these query relates specifically to multiple EMIS Partner API connections from the same server setup, we recommend contacting the EMIS Partner Support team directly, as the NHS England’s API Platform is not able to assist with EMIS-native behaviour or permissions.

You could also look at :
Checking and clearing Local Activation Cache / Registry,
Isolate Each Practice’s Configuration,
Check Product mapping as same Product ID can be used for multiple practices, each practice must be explicitly mapped to your product within EMIS’s Partner API control panel.

If these issues persist, we recommend raising this directly with EMIS Partner Support for confirmation on what’s supported and what your product is currently authorised to do.

EMIS Partner API Support

Hope the above helps.

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API specific queries, please reach out the relevant API teams.

5

Hi @navin.bose

Hope you’re well. I’m uploading attachments via the EMIS FileRecord API. Multiple small files work fine, but larger uploads fail—for example, 5 files of ~10 MB each return “413 Request Entity Too Large.”

Could you confirm the maximum allowed size per file and per request?

Thanks,

6

Hi Ali,

The 413 Request Entity Too Large error is generated by EMIS’s Partner API gateway when a request exceeds the configured maximum payload size. With the FileRecord API, there are two important limits to be aware of:

File size limits

Maximum per individual file: typically 10 MB
Maximum per request (aggregate of all files in the submission): around 25 MB

Recommended approach

  • Keep each file under 10 MB.
  • Ensure the combined request payload does not exceed ~25 MB.
  • For larger documents, split them into smaller chunks or submit them in multiple requests.

If you have a clinical use case that consistently requires handling larger file sizes (e.g. radiology or imaging attachments), I’d recommend raising this with the EMIS API Support team - they can confirm whether higher limits are possible for your integration.

Hope the above helps.

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API specific queries, please reach out the relevant API teams.

7

Hi,

Thank you for the clear explanation, really helpful.

In my testing, I hit a 413 when the combined payload was approximately 15.4 MB (three files). So now I am going to try to split large requests and send multiple requests.

Could you also confirm whether there’s an environment-specific cap around approx 15? If higher limits are possible for our clinical use case, I’m happy to raise this with EMIS API Support.

Thanks again, I really appreciate the help.

Thanks

8

The 413 errors are consistent with how EMIS enforce request size caps across different environments.

Environment-specific caps:

  • In INT/UAT environments, the payload cap is often set lower (around 15 MB total request size) to protect shared test infrastructure.
  • In Production, the request limit is typically higher (around 25 MB aggregate), while still enforcing the 10 MB per individual file rule.

The above would explain why you’re hitting a 413 in INT at ~15.4 MB.

Following the recommended approach to keep each file under 10 MB and not to exceed the combined request payload of ~25 MB - should help to work around the environment limitations.

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API specific queries, please reach out the relevant API teams.

9

Thank you for the clarification and detailed explanation. This helps a lot.