# Clarification on OAuth 2.0 Client Creation Policy for Companies House Test Environment

**URL:** <http://forum.companieshouse.gov.uk/t/clarification-on-oauth-2-0-client-creation-policy-for-companies-house-test-environment/12200>\
**Category:** API Question\
**Created:** [October 7, 2025, 1:24pm UTC](http://forum.companieshouse.gov.uk/t/clarification-on-oauth-2-0-client-creation-policy-for-companies-house-test-environment/12200 "2025-10-07T13:24:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![productivelydev](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/p/3ec8ea/32.png) [@productivelydev](http://forum.companieshouse.gov.uk/u/productivelydev)\
**Post date:** [October 7, 2025, 1:24pm UTC](http://forum.companieshouse.gov.uk/t/clarification-on-oauth-2-0-client-creation-policy-for-companies-house-test-environment/12200/1 "2025-10-07T13:24:31Z")

</div>

We’re integrating our product **Productively** with the **Companies House API** via **OAuth 2.0**. Before proceeding, we’d like clarification on the current **policy and limitations** around creating **OAuth clients** in the **Test (sandbox)** environment.

Specifically:

- Are **OAuth Web Clients** currently disabled or restricted in the beta Developer Hub?
- Is there a separate approval process or permission needed for access?
- Can Companies House support create a **test OAuth client** for us manually until the issue is resolved?

Our goal is to complete our integration testing with valid `client_id` and `client_secret` credentials before moving to production.