10.Creating, Publishing & Testing an API in WSO2 APIM v4 - Part 1
HTML-код
- Опубликовано: 19 сен 2024
- This video demonstrates how to create, publish and test an API via a privileged user (admin)-
1. Create an API
2. Publish & Test via Publisher Portal
3. Testing via Devportal, cURL & Postman
Kindly refer to my Blog for more WSO2 contents: k10technical.b...
Full Playlist- • 1. WSO2 API Manager v4...
I have a problem when I'm on the runtime screen. I select only the API key, but when I try to request the data, it does not work. It requires the authorization header with the access token, and I don't know why
Please check in publisher portal > API > Runtime configuration you have enabled APIKey option.
Ref: apim.docs.wso2.com/en/4.1.0/assets/img/learn/api-key-option.png
Great content, can you please provide example for POST method as well
Thanks for your compliments! If you are using the pizza shake api for testing then respective POST,PUT, DELETE operations ab be tried out via devportal tryout console. Let me know if you want further assistance.
Good job
Thanks!
@@wso2bytes Could you do the video series for IS & Micro integrator as well. Do a use case scenario . Thanks
Glad to see the content helpful. Sure will plan for MI & IS soon!
@@wso2bytes its really easy to understand while you explain the concept .Keep it up
thanks for this great work
please i am getting a cors error "CORS Network Failure URL scheme must be "http" or "https" for CORS request". how do i handle this.
Can you please try using postman or cURL and it should work.
@@kumargaurav7044 here is the response I got from postman "code": "404",
"type": "Status report",
"message": "Not Found",
"description": "The requested resource is not available."
The error indicates the API hasn't been published to the gateway and hence the respective resource is not available. Is this PizzaShake API? Can you please check and publish and then it should be
@@wso2bytes this Mocky api, i Just created a new one and published but still the same error
I have the same problem, when I keep the domain name as "localhost" I don't get this problem but when I change the domain name I get this error, even though I have the CORS option enabled.
while testing a newly created mocky endpoint through WSO2 Publisher post deployment i am getting CORS error...kindly let me know what to do in such case
Can you please confirm from which client you are testing the API and is it token based or apikey based api testing?
@@wso2bytes for internal also
hello mate thanks for this video,
I have a problem when testing my API on the portlal I get 403 not authorized error ! i made subscription like you did and follewed your steps ! please help me
403
Undocumented
Error: Forbidden
Response body
Download
{
"code": "900908",
"message": "Resource forbidden ",
"description": "User is NOT authorized to access the Resource. API Subscription validation failed."
}
403 is usually associated with permission issue. Can you pls first try with admin user I.e. login to devportal using admin user, subscribe the api with Default Application and test the api?