developer does not see published api

[#1]

Hello, I have apigee edge account. Created simple api from soap-to-rest service.

Can successfully call new service. But how to publish service definition for the developer?

I want him to see endpoints, operations, verbs that are published for my simple api...

I requested a dev portal and finally got it.

But I still don't see APIs published for the developer on my dev portal.

As app developer I can see my app, product but not the api !

Regards,

Dmitry

[anilsr]

Dear @Dmitry Lukyanov ,

Welcome to Apigee Community 🙂

You can publish API documentation using Apigee Developer Portal smartdocs. You need Open API Spec (Swagger) / WADL spec for your API proxy to generate SmartDocs which will have all the details regarding your API. Users can also call the API & see the response from smartdocs.

You can find more information regarding setting up API documentation in developer portal using smartdocs here. For Example, See smartdocs in action here.

Keep us posted if you have any queries while implementing same.

[#3]

Anil Sagar, thanks for your reply.

So api definition publishing is not automatic and i have to upload wadl/swagger for each api.

right?

What about rest-to-soap proxy?

the apigee code generated automatically from my wsdl.

how can i get the wadl or swagger for automatically generated proxy service?

Regards,

Dmitry

[anilsr]

@Dmitry Lukyanov , That's correct. API Definition publishing is not automated today. You have to upload WADL / Swagger.

Yes, Apigee Edge has feature which converts soap to rest. If you would like to generate Swagger / WADL from Apigee Edge proxies please take a look at open source tools written by Apigeeks.

• Apigee2Swagger :
  • Command line tool that converts Apigee API Proxy Bundle to swagger spec 2.0 file .
  • Built on Node.js
  • It will help to generate Swagger 2.0 spec for Apigee Developer Portal Smartdocs.
  • Find more detailed article here on using same.
• API2Swagger :
  • Swagger 2.0 Specification Generator
  • CURL Like command syntax
  • Support JSON/Plain text request/response
  • Support for GET / POST / PUT / DELETE http method
  • Saves lot of time, changes the way you write API documentation / display same using smartdocs / swagger UI
  • Runs on local machine, built on top of Node.JS
  • Find more about same here
• Apigee API Model Generator
  • Generates WADL

Keep us posted if you have any queries using above tools.

[#5]

@Anil Sagar

can you pleas tell how to change 'portal' base url

I have create and 'SPEC' then generated one proxy out of it,

After this I created one 'product'

Then in create one 'Portal' and loaded 'my product' into it

every thing works good.

Independently my proxy work

however from my developer portal I am not able to get proper response for 'Try It' option over developer portal

The reason that might be is Base url different on developer portal

Consider the following:

for this url:

https://prasad226-test.apigee.net/v1/vakratunda/login.php?usrname=7058420909&classid=5

I am getting :

curl -X GET "https://prasad226-vakratundaandroid.apigee.io/vakratunda/login.php?usrname=7058420909&classid=1" -H "accept: application/json"

And response is HTML. please tell me how to change base url for developer portal/api doc

[rdeandrade]

Hi Prasad, this should actually go as a new question in the forum.

Here are a few pointers, and if you are still stuck, please ask as a new question.

There may be a few places you need to configure to get the custom domain working:

1. your API - setup a new vhost with the desired domain and reference them in your API Proxy

2. your docs - make sure that in your spec you have the base url pointing to the same URL as defined in your APIs (look for schemes, host and paths in the spec)

reference:

http://docs.apigee.com/api-services/content/virtual-hosts

https://docs-new.apigee.com/custom-domain