Connect Api Key
Changed onConnect a custom (API-key) source, e.g. Adapty.
There is no OAuth popup: the customer pastes their secret key, the backend imports it into Nango's vault, then proves it works before saving anything. A key that Nango accepts but the provider rejects must not leave a live connection behind, so a failed verification rolls the stored key back.
Request
- Base URL: https://api.heymetra.com (the document declares no server; this is the origin it was published from)
- URL: https://api.heymetra.com/api/connections/{provider}/api-key
- Auth: none declared
Path parameters
Headers
Request body
Response
Successful Response
Changes
- warning
added the new
ikasenum value to theresponse property for the response status - info
added the new enum value
ikasto thepathrequest parameterprovider
- warning
- warning
added the new
amazon_sellerenum value to theresponse property for the response status - warning
added the new
ciceksepetienum value to theresponse property for the response status - warning
added the new
hepsiburadaenum value to theresponse property for the response status - warning
added the new
n11enum value to theresponse property for the response status - info
added the new enum value
amazon_sellerto thepathrequest parameterprovider - info
added the new enum value
ciceksepetito thepathrequest parameterprovider - info
added the new enum value
hepsiburadato thepathrequest parameterprovider - info
added the new enum value
n11to thepathrequest parameterprovider
- warning