{ Community }
  • Academy
  • Docs
  • Developers
  • Resources
    • Community Articles
    • Apigee on GitHub
    • Code Samples
    • Videos & eBooks
    • Accelerator Methodology
  • Support
  • Ask a Question
  • Spaces
    • Product Announcements
    • General
    • Edge/API Management
    • Developer Portal (Drupal-based)
    • Developer Portal (Integrated)
    • API Design
    • APIM on Istio
    • Extensions
    • Business of APIs
    • Academy/Certification
    • Adapter for Envoy
    • Analytics
    • Events
    • Hybrid
    • Integration (AWS, PCF, Etc.)
    • Microgateway
    • Monetization
    • Private Cloud Deployment
    • 日本語コミュニティ
    • Insights
    • IoT Apigee Link
    • BaaS/Usergrid
    • BaaS Transition/Migration
    • Apigee-127
    • New Customers
    • Topics
    • Questions
    • Articles
    • Ideas
    • Leaderboard
    • Badges
  • Log in
  • Sign up

Get answers, ideas, and support from the Apigee Community

  • Home /
  • Developer Portal (Integrated) /
avatar image
0
Question by sharped · Dec 08, 2020 at 03:12 PM · 55 Views SmartDocsintegrated portalopenapi

SmartDocs in Integrated query build the incorrect API request

Hi,

I have created OpenAPI yaml files for our APIs and validated them using https://apitools.dev/swagger-parser/online/ and https://editor.swagger.io/. Having established that the OpenAPI spec that I had created worked as I hoped when rendered by editor.swagger I uploaded it into our integrated portal. However, after a few tests I established that in cases where I want to pass multiple parameters into a url the integrated portal doesn't seem to interpret the API spec in the same way as the tools I was using.

Expected behaviour, selecting 3 query parameters builds the following query:

'https://api.rsc.org/compounds/v1/records/{id}/details?fields=param1,param2,param3'

where the parameters are comma delimited

What I see when I try to use the SmartDocs in the portal is:

'https://api.rsc.org/compounds/v1/records/{id}/details?fields=param1&fields=param2&fields=param3'

.... which results in the API endpoint only accepting the 1st parameter.

I am using the following fields in my OpenAPI spec:

style: "form"

explode: false

The full spec is available at:

https://developer.rsc.org/portals/api/sites/rsc-developerportal/liveportal/apis/compounds-v1-trial/download_spec

Can anyone advise if this is an issue with the SmartDocs, and provide details as to how to get the Developer Portal to build the request that my APIs expect?

Comment
Add comment
10 |5000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by Apigeeks only
  • Viewable by the original poster
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Close

0 Answers

  • Sort: 

Follow this Question

Answers Answers and Comments

48 People are following this question.

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Related Questions

Know Issue: formData parameter in OpenAPI 3.0 spec is not displayed in Integrated Portal 0 Answers

Remove reCAPTCHA from dev portal login page 2 Answers

Changing the API spec in the Integrated Portal APIs section does not work properly 3 Answers

Integrated Developer Portal (become a developer) 1 Answer

integrated developer portal management API 0 Answers

  • Products
    • Edge - APIs
    • Insights - Big Data
    • Plans
  • Developers
    • Overview
    • Documentation
  • Resources
    • Overview
    • Blog
    • Apigee Institute
    • Academy
    • Documentation
  • Company
    • Overview
    • Press
    • Customers
    • Partners
    • Team
    • Events
    • Careers
    • Contact Us
  • Support
    • Support Overview
    • Documentation
    • Status
    • Edge Support Portal
    • Privacy Policy
    • Terms & Conditions
© 2021 Apigee Corp. All rights reserved. - Apigee Community Terms of Use - Powered by AnswerHub
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Post an idea
  • Spaces
  • Product Announcements
  • General
  • Edge/API Management
  • Developer Portal (Drupal-based)
  • Developer Portal (Integrated)
  • API Design
  • APIM on Istio
  • Extensions
  • Business of APIs
  • Academy/Certification
  • Adapter for Envoy
  • Analytics
  • Events
  • Hybrid
  • Integration (AWS, PCF, Etc.)
  • Microgateway
  • Monetization
  • Private Cloud Deployment
  • 日本語コミュニティ
  • Insights
  • IoT Apigee Link
  • BaaS/Usergrid
  • BaaS Transition/Migration
  • Apigee-127
  • New Customers
  • Explore
  • Topics
  • Questions
  • Articles
  • Ideas
  • Badges