Bug Description

curl -X POST https://sandbox.hyperswitch.io/v2/customers
-H "api-key: snd_{api-key omitted}"
-H "Content-Type: application/json"
-d '{
"email": "guest@example.com",
"name": "John Doe"
}'
{"error":{"type":"invalid_request","message":"Missing required param: Authorization","code":"IR_04"}}

v2 should only require the api-key in the header. It fails on the demonstration documentation as well. This is a breaking issue because you cannot utilize the Payment Method Management system without a v2 customer id.

Expected Behavior

v2 should only require the api-key in the header.

Actual Behavior

It sends a missing header param 'Authorization' but should not be required.

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

1. Go to '(https://api-reference.hyperswitch.io/v2/customers/customers--create)'
2. Try and input your api-key and customer name/email
3. See error response

Context For The Bug

This is a breaking issue because you cannot utilize the Payment Method Management system without a v2 customer id. The PMM process fails utilizing a v1 customer_id so I tried to change to utilize the v2 method, and ran into this issue. I cannot proceed forward to utilize the SDK.

Environment

Are you using hyperswitch hosted version? Yes
If yes, please provide the value of the x-request-id response header to help us debug your issue.
(019b5734-9491-7c51-88ee-a3325b5c6d99, 019b5732-c932-7841-a28d-6533e8421061)

Have you spent some time checking if this bug has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

No, I don't have time to work on this right now