@Raja Rakesh Kumar, I believe you are seeing this for verifyApikey policy ? Is that same for your GET and POST . AFAIK you will see this issue when your ref in verifyApikey is null .
Yes @Raja Rakesh Kumar you have to use a query param to send it. Alternatively you can also can send it in the header & then you will change the verify api key policy to read it from the header. For eg: If you set a header named api-key, you can reference it in the verify api key policy as request.header.api-key. Hope this helps.
Can you please attach your proxy bundle to better understand your issue ? Looks like targer server don’t accept POST method & above error is response from target. You can trace the call in Apigee Edge proxy to find out what’s going on.
I’m having a similar issue as @Richmond Faustino , however, it’s occurring in the extra credit section of the APIKEY part of the tutorial, not anything custom (iow, the target server @ apigee). If you can be more specific about what you need to see as an attachment, I’m happy to add…
@Prithpal Bhogill - added trace. Test conducted entirely within Apigee console, not postman
I’m having a similar issue as @Richmond Faustino , however, it’s occurring in the extra credit section of the APIKEY part of the tutorial, not anything custom (iow, the target server @ apigee). If you can be more specific about what you need to see as an attachment, I’m happy to add…
@Prithpal Bhogill - added trace. Test conducted entirely within Apigee console, not postman