check-vat-number API Failing

[mPisano]

https://api.service.hmrc.gov.uk/organisations/vat/check-vat-number/lookup/1234567890

{"code": "MATCHING_RESOURCE_NOT_FOUND", "message": "A resource with the name in the request can not be found in the API"}

Bug report

You must read the information below before you submit a bug report.

The MTD API team cannot help if your bug report is about:

• Fraud Prevention Headers
• Issues relating to OAuth2
• Subscribing or registering to use the API Platform, MTD enrolment, de-enrolment, registration for VAT, Beta services, etc.
• Issues integrating with the API Platform (e.g. setting up an application/access)
• Code examples in a given programming language
• Business-related questions or processes pre MTD
• Scheduled maintenance windows and days
• Onboarding (e.g. registering, obtaining keys)
• Performance metrics

For any of the above, you must contact the Software Developer Support Team directly at SDSTeam@hmrc.gov.uk. The SDS Team do not monitor this repository.

This repository is for bug reports relating to VAT API code in this repository only.

Fill in the sections below to submit your bug report:

• Documentation
• API

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots / Requests / Responses
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[mPisano]

Self Follow-Up - Seems No More API 1.0 :(
https://developer.service.hmrc.gov.uk/api-documentation/docs/api/service/vat-registered-companies-api/2.0

This seems very unfair!

Anybody can check a VAT here:
https://www.tax.service.gov.uk/check-vat-number/enter-vat-details

But now we have to register our Application with HMRC and get approval?!?!?
Worse is now need OAuth 2.0 and TLS instead of a simple Web API call!

Bad Direction for an API that intended to simply verify a VAT number like the EORI Check... or is that next!

Can somebody at HMRC explain WHY?????

[AllanJard]

Completely agree - this is a really poor change. A simple VAT number validation call should not require OAuth authentication. I've send feedback via their form and if I hear back I'll update here. Considering writing to my MP about this as well, but 99% sure I'd get nothing but a canned reply back. I think it is fair enough for OAuth to be needed for the address lookup, but simply checking if a number is a valid VAT number or not, that should be a trivial unauthenticated GET request, exactly as it used to be.

[mPisano]

Luckily I did have an HMRC login for a different application and was able to add this API, I feel bad for those who don’t.

https://developer.service.hmrc.gov.uk/api-documentation/docs/api/service/vat-registered-companies-api/2.0

I think the V1 of the VAT API should return without the ability to “request a receipt” flag.
Just a simple number lookup, without receipts for the world . Creating them and tracking was probably too much for HMRC…
V2 should be Mode 2 with receipts using OAUTH while they “fully understand our users”

[AllanJard]

The reply from HMRC:

I appreciate your frustration, however there're multiple reasons why this change was necessary; such as ensuring we have a comprehensive understanding of our service users. I will however pass this on as feedback.

If you already have a production application, you can add the Check A UK VAT Number v2.0 API subscription. If you do not, you will need to create an application. Guidance can be found here on the HMRC Developer Hub.

The registration process typically takes around two weeks but may take longer if additional information is required. Please also complete and return the attached checklist.

I don't agree that they need to understand the users of their service for a VAT number validation check. But what do I know. I don't have an application already, I don't need to submit VAT returns or anything like that, I just want to validate a VAT number. I've simply disabled that check for now - being in the UK it makes little difference (if the purchaser wants to enter nonsense as their VAT number it makes no difference to me, they will be charged VAT anyway).

Its another barrier to entry and more red tape though, and I'm finding this very frustrating.

[niroboo]

Do you need approval before you can use the sandbox url? Is the documentation not correct?
I created a new integration, following the V2 documentation (never used V1) but I still get the same error.

1. Get token

POST https://test-api.service.hmrc.gov.uk/oauth/token
Content-type: application/x-www-form-urlencoded

client_secret=[YOUR-CLIENT-SECRET]&client_id=[YOUR-CLIENT-ID]&grant_type=client_credentials&scope=read:vat

2. Call API

GET https://test-api.service.hmrc.gov.uk/organisations/vat/check-vat-number/lookup/553557881
Accept: application/vnd.hmrc.2.0+json
Authorization: Bearer <valid access-token from step 1>

Response (404):

{
  "code": "MATCHING_RESOURCE_NOT_FOUND",
  "message": "A resource with the name in the request can not be found in the API"
}

[niroboo]

Self Follow-Up - the openapi-generator I used didn't actually set the Accept header to the given value and defaults to application/json which apparently results in a 404 MATCHING_RESOURCE_NOT_FOUND.
Not a very informative way of letting the consumer know a application/json is not accepted.

Leaving this up here in case anyone else ran into the same problem.

[KenRandall]

You can't argue with these people. Just the same reason they need to know the screen size people are using!!!