Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Plane API not be consistent with service call #26

Open
wenytang-ms opened this issue Jul 16, 2024 · 3 comments
Open

Data Plane API not be consistent with service call #26

wenytang-ms opened this issue Jul 16, 2024 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@wenytang-ms
Copy link
Contributor

Hi team
In this doc, it says that The portal uses the [Azure API Center data plane API](https://learn.microsoft.com/en-us/rest/api/dataplane/apicenter/operation-groups) to retrieve data from your API center.
But in the runtime, I tried with the json configuration

{
  "dataApiHostName": "<service name>.data.<region>.azure-apicenter.ms/workspaces/default",
  "title": "API portal",
  "authentication": {
      "clientId": "<client ID>",
      "tenantId": "<tenant ID>",
      "scopes": ["https://azure-apicenter.net/user_impersonation"],
      "authority": "https://login.microsoftonline.com/"
  }
}

it seems not same as the Data Plane Api's domain defined as https://{serviceName}.data.azure-apicenter.net like such as List All APIs

I'm confuse that is there any mistake?

@wenytang-ms
Copy link
Contributor Author

I guess this is a mistake that doc teams leave an outdate domain in the rest api.

@pierceboggan pierceboggan added the documentation Improvements or additions to documentation label Jul 31, 2024
@pierceboggan
Copy link
Contributor

Thanks for the report! We're updating our documentation to resolve this now.

@DBuijse
Copy link

DBuijse commented Aug 2, 2024

I saw this issue and realized I also probably used the wrong domain.
After configuring it to the "https://{serviceName}.data.azure-apicenter.net" format I no longer get a 404 but a (failed)net::ERR_EMPTY_RESPONSE .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants