Small and medium business | Business Central, N...

Custom API Page fails to become registered on Deployment to BC Sandbox

(1) Share

Report

Posted on by CS-15050100-0

Hi All,

I am creating a custom version of the vendorPaymentJournals API. When I deploy it to BC from VSCode, it is failing to become registered as a service when I set the APIPublisher to a specific value. When I change the APIPublisher, it will end up working.

Here is a look at the API page

It does not appear as an endpoint when I run a GET request to following uri in Postman.

https:/api.businesscentral.dynamics.com/v2.0/{{Tenant_ID}}/{{Environment}}/api/waveKraft/integration/v2.0/

When I attempt a GET to the endpoint of the API page above like so...

https:/api.businesscentral.dynamics.com/v2.0/{{Tenant_ID}}/{{Environment}}/api/waveKraft/integration/v2.0/companies({{Cronus_Comp_ID}})/vendorPaymentBatches

I get the following error

{

/error/: {

/code/: /BadRequest_NotFound/,

/message/: /No HTTP resource was found that matches the request URI 'https:/api.businesscentral.dynamics.com/v2.0/{{Tenant_Id}}/{{Environment_Name}}/api/waveKraft/integration/v2.0/companies({{Company_Id}})/vendorPaymentBatches?tenant={{Tenant}}'./

}

When I adjust the APIPublisher to something like 'kraft', it will work. I have a series of other custom APIs working with the exact same combination of APIGroup, APIPublisher, and APIVersion, namely, 'integration', 'waveKraft', and 'v2.0'.

Any ideas anyone can provide on what my issue might be would be much appreciated.

Thanks!

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Gerardo Rentería Ga... 25,398 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi

I think you need to complete this in the URL "//"

BR

GR

Was this reply helpful? Yes No
CS-15051251-0 59 on at

Like (0)

Report
Copy link

Link copied!

Hi gdrenteria, thanks for the response. I am not sure I understand your comment though. You are referring to the vendorPaymentBatches url? Not sure what you mean "complete this '//'". The url I am using for that GET request does not seem to be the issue because when I change the APIPublisher on the API page and then publish my extension, I just tweak the publisher portion of my url and it works.

Thanks

Was this reply helpful? Yes No
soma 24,410 on at

Like (0)

Report
Copy link

Link copied!

Hi @CS-15051251-0,

Did you get a chance to fix this issue? I am also facing the same issue.

I have deployed 15 new custom APIs(all are having same APIGroup and APIPublisher), but only able to access 10 APIs.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 21,073 Super User 2025 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Not sure if it helps or not: https://yzhums.com/52262/

Was this reply helpful? Yes No