Clarification and Setup Instructions for Enterprise-Wide Use of Companies House API Key

I hope this message finds you well. I am reaching out to discuss the transition of certain APIs from development to production use within our enterprise. We have been utilizing the following APIs for development purposes:

  1. Company Search: ****
  2. Company Details: ****
  3. Company Officers: ****
  4. Persons with Significant Control (PSC) Data: ****
  5. Document List: ****

Currently, we are accessing these APIs with the following credentials:

  • Username: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  • API Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

As we prepare for the production deployment, I would like to clarify whether a new API key is required for enterprise-wide use, or if the existing key can be extended for this purpose. Understanding the best practices and any necessary steps for this transition is crucial for us.

Can i get a response for this?

A live API key is a live API key. How you use it is a matter for you to decide.
We have found that many of our customers tend to separate out dev/test keys/accounts from their live key/accounts as part of deployment.