SQL Server
SQL Server
Refresh Wish for Merchants OAuth2 Access Token
See more OAuth2 Examples
Demonstrates how to refresh a Wish OAuth2 access token.Note: This example requires Chilkat v9.5.0.85.
Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
-- Important: Do not use nvarchar(max). See the warning about using nvarchar(max).
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- This example requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
-- See Get Wish OAuth2 Access Token
-- for sample code showing how to obtain a Wish access token for desktop apps.
-- This example assumes we previously obtained an OAuth2 access token for Wish.
DECLARE @jsonToken int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonToken OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
EXEC sp_OAMethod @jsonToken, 'LoadFile', @success OUT, 'qa_data/tokens/wish.json'
IF @success <> 1
BEGIN
PRINT 'Failed to load wish.json'
EXEC @hr = sp_OADestroy @jsonToken
RETURN
END
-- The access token JSON looks something like this:
-- {
-- "message": "",
-- "code": 0,
-- "data": {
-- "access_token": "15af1c191c1243b029bc1660b5c08ce7",
-- "scopes": [
-- "epc:read",
-- "epc:write",
-- "fbs:read",
-- "fbs:write",
-- "fbw:read",
-- "fbw:write",
-- "infractions:read",
-- "infractions:write",
-- "insurance:read",
-- "insurance:write",
-- "loans:read",
-- "loans:write",
-- "merchant:read",
-- "merchant:write",
-- "notifications:read",
-- "notifications:write",
-- "orders:read",
-- "orders:write",
-- "payments:read",
-- "payments:write",
-- "penalties:read",
-- "penalties:write",
-- "product_boost:read",
-- "product_boost:write",
-- "products:read",
-- "products:write",
-- "ratings:read",
-- "ratings:write",
-- "returns:read",
-- "returns:write",
-- "tickets:read",
-- "tickets:write"
-- ],
-- "merchant_id": "5eb3f605178f5be2c784fa02",
-- "expiry_time": "2020-12-17T16:55:09.594+00:00",
-- "refresh_token": "55a38e44df674a1e859891624b2c4c23"
-- }
-- }
DECLARE @oauth2 int
EXEC @hr = sp_OACreate 'Chilkat.OAuth2', @oauth2 OUT
-- Note: In most OAuth2 implementations, the token endpoint is the same for both the
-- refresh request and the exchange-code-for-token request (which happens when getting
-- the OAuth2 token for the 1st time). Wish uses a different URL for the refresh:
EXEC sp_OASetProperty @oauth2, 'TokenEndpoint', 'https://merchant.wish.com/api/v3/oauth/refresh_token'
-- The following uncommon option was added in Chilkat v9.5.0.85
EXEC sp_OASetProperty @oauth2, 'UncommonOptions', 'EXCHANGE_CODE_FOR_TOKEN_USING_GET'
-- Replace these with actual values.
EXEC sp_OASetProperty @oauth2, 'ClientId', 'WISH-CLIENT-ID'
EXEC sp_OASetProperty @oauth2, 'ClientSecret', 'WISH-CLIENT-SECRET'
-- Get the "refresh_token"
EXEC sp_OAMethod @jsonToken, 'StringOf', @sTmp0 OUT, 'data.refresh_token'
EXEC sp_OASetProperty @oauth2, 'RefreshToken', @sTmp0
-- Send the HTTP request to refresh the access token..
EXEC sp_OAMethod @oauth2, 'RefreshAccessToken', @success OUT
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @oauth2, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @jsonToken
EXEC @hr = sp_OADestroy @oauth2
RETURN
END
-- Save the new JSON access token response to a file.
-- The access + refresh tokens contained in this JSON will be needed for the next refresh.
DECLARE @sbJson int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbJson OUT
EXEC sp_OAGetProperty @oauth2, 'AccessTokenResponse', @sTmp0 OUT
EXEC sp_OAMethod @sbJson, 'Append', @success OUT, @sTmp0
EXEC sp_OAMethod @sbJson, 'WriteFile', @success OUT, 'qa_data/tokens/wish.json', 'utf-8', 0
PRINT 'OAuth2 token refreshed!'
EXEC sp_OAGetProperty @oauth2, 'AccessToken', @sTmp0 OUT
PRINT 'New Access Token = ' + @sTmp0
EXEC @hr = sp_OADestroy @jsonToken
EXEC @hr = sp_OADestroy @oauth2
EXEC @hr = sp_OADestroy @sbJson
END
GO