Invoke API in new light weight Developer Portal

Google Cloud Apigee
1

Hi guys, I am working on Apigee light weight Portal.

  • I have created an API, Product & Portal.
  • In Portal I have added the above Product along with Swagger Specification.
  • In Portal i can see the API operations as per Swagger in APIs Tab.
  • I logged in created an APP added a product and got API keys.
  • Now how can I invoke the APIs in Portal?
  • Is there any API Console available in Portal or does it use Swagger Console?

@Anil Sagar

1 Like
2

@Barahalikar Siddharth , It’s not supported yet. We don’t have any ETA.

@marshg@google.com might know about same.

3

I am surprised to read that, it doesn’t support invoking API as it supports creating Apps & getting credentials. I searched all related Apigee docs & thought I missed something to invoke the APIs :smiley:

Anyway this Portal is very easy to setup compared to full-fledged Drupal Portal.

Meanwhile can you please un-freeze my old drupal portal if possible,

http://dev-siddharth1.devportal.apigee.com/

4

@Barahalikar Siddharth requested site has been unfrozen. Please note that the new url is : http://dev-siddharth1.devportal.apigee.io/ - Arun

5

We are also looking for this functionality in the light weight portal. If possible, please post back to this thread if there are any updates on the ETA for this feature.

6

Hi @Siddharth Barahalikar,

The API Portals now support a Try It feature but there is a caveat, your APIs need to support CORS.

If you use the “Try it out” button and see “TypeError: Failed to fetch” in the response, then you know you need CORS.

If your not already familiar with how to implement CORS, see: https://community.apigee.com/questions/21538/cors-preflight-and-passing-cors-header-in-response.html

7

Yes @Kurt Kanaskie I am aware of it. I noticed it in November 2017, when I was working on new use case.

Anyway thanks for bringing it up, people referring to this post might get teh solution.

8

FYI: The same “Undocumented” error “TypeError: Failed to fetch” may be issued for other reasons.

  1. If you access the lightweight portal APIs via https (default) and your swagger call indicated the “http” scheme. Check Chrome console for message

Mixed Content: The page at ‘https://xxxx..’ was loaded over HTTPS, but requested an insecure resource ‘http://xxxx…’. This request has been blocked; the content must be served over HTTPS.

  1. If the Target Server response is 302 (Found / Document moved) - may trigger CORS issues

  2. Any response not a 200 Okay may also be reflected as failed to fetch.

9
  1. Unlisted header. I was passing the App key …
Request header field x-api-key is not allowed by Access-Control-Allow-Headers

The default CORS policy does not include this as one of the allowed headers :slight_smile: