Forum Discussion
Thanks chichepo This was very helpful. Here is an update -
1. Versioning resolved. all set there.
2. Regarding authentication - I don't have Okta to be tied to it. Can i use something to behave like dummy authentication? I just want to make sure my request and responses work. Currently, I have defined request and responses in swagger but unable to feature "try it out" as I get an error
Error: response status is 404 Response bodyResponse headerscache-control: no-cache content-length: 0 content-type: application/octet-stream date: Thu,16 Mar 2023 16:49:16 GMT etag: W/"0-2jmj7l5rSw0yVb/vlWAYkK/YBwk" expires: -1 status: 404 Not Found |
Related issues with #2: I have defined my request and response for application/json but I see
content-type: application/octet-stream in response when I execute the endpoint.
Here is my configuration:
paths:
/portfolios:
post:
tags:
- portfolio
summary: create a new portfolio
description: >-
This endpoint creates a new portfolio in the system with its unique name and enumeration.
operationId: addPortfolio
requestBody:
description: Create a new portfolio in the system.
content:
application/json:
schema:
$ref: '#/components/schemas/create-portfolio'
required: true
responses:
'200':
description: Portfolio created successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/portfolio-created'
Your quick response is much appreciated.
pathaniaamn
You can define a dummy authenticaton.
|
Try the simplest one: apiKey
Regarding the issue in the response content type, it depends on the server application.
You can, of course, change your API specification with content-type: application/octet-stream if it makes sense in term of behavior expectation.
If not, you should ask your backend app developper to modify the output payload content format to Json
Related Content
- 4 years agoCapricornus
- 2 years agolalit_singh
Recent Discussions
- 3 hours agokj20nt