(SQL Server) MyInvois Malaysia Login as Intermediary System

See more Malaysia MyInvois Examples

Demonstrates how to get an OAuth2 access token with an intermediary that is representing a taxpayer (acting on behalf of a specific taxpayer). The OAuth2 access token can then be used to access MyInvois protected APIs.

For more information, see https://sdk.myinvois.hasil.gov.my/api/08-login-as-intermediary-system/

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This example requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    -- Sends the following HTTP POST to get a MyInvois OAUth2 access token using client_credentials

    -- POST /connect/token HTTP/1.1
    -- Host: preprod-api.myinvois.hasil.gov.my
    -- Accept: */*
    -- Content-Length: <<variable>>
    -- Content-Type: application/x-www-form-urlencoded
    -- 
    -- client_id={YOUR_CLIENT_ID}&client_secret={YOUR_CLIENT_SECRET}&grant_type=client_credentials&scope=InvoicingAPI

    -- --------------------------------------------------------------------------------------------------------
    -- Note: There is a large amount of information about the MyInvois API on the Internet.
    -- The information is found at https://sdk.myinvois.hasil.gov.my/
    -- and also at many other companies offering solutions.
    -- 
    -- Unfortunately, it's all completely useless to the programmer wishing to implement the API.
    -- The reason it's useless is because no specifics are given.
    -- A developer needs to know the specific details of the HTTP request and response.
    -- What is the HTTP request Content-Type?
    -- What is the endpoint?
    -- What is the format of request body and response?  JSON or XML?
    -- What specific header fields are needed, if any?
    -- 
    -- Providing samples of raw HTTP requests and responses tells the developer everything he/she needs to know.
    -- All unknowns become known.  
    -- Everything becomes easy to implement.
    -- Just show some sample raw HTTP requests and responses, and we can all spend far less time in the office
    -- and more time relaxing on a beach.

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Http', @http OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @req int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.HttpRequest', @req OUT

    EXEC sp_OAMethod @req, 'AddParam', NULL, 'grant_type', 'client_credentials'
    EXEC sp_OAMethod @req, 'AddParam', NULL, 'client_id', 'YOUR_CLIENT_ID'
    EXEC sp_OAMethod @req, 'AddParam', NULL, 'client_secret', 'YOUR_CLIENT_SECRET'
    EXEC sp_OAMethod @req, 'AddParam', NULL, 'scope', 'InvoicingAPI'

    DECLARE @resp int
    EXEC sp_OAMethod @http, 'PostUrlEncoded', @resp OUT, 'https://preprod-api.myinvois.hasil.gov.my/connect/token', @req
    EXEC sp_OAGetProperty @http, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        RETURN
      END

    -- Note: The returned access token is valid for a short amount of time.  Perhaps 1 hour.
    -- The access token is used in the "Authorization: Bearer <access_token>" header in subsequent requests until it expires.
    -- Your application would then need to get a new access token, and so on..


    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    PRINT 'Response Status Code: ' + @iTmp0

    PRINT 'Response Body:'
    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    PRINT @sTmp0

    -- Here's a sample response:

    -- {
    --   "access_token": "eyJhbGciOiJSUzI1...",
    --   "expires_in": 3600,
    --   "token_type": "Bearer",
    --   "scope": "InvoicingAPI"
    -- }

    DECLARE @json int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.JsonObject', @json OUT

    DECLARE @success int
    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    EXEC sp_OAMethod @json, 'Load', @success OUT, @sTmp0
    DECLARE @access_token nvarchar(4000)
    EXEC sp_OAMethod @json, 'StringOf', @access_token OUT, 'access_token'
    DECLARE @expires_in int
    EXEC sp_OAMethod @json, 'IntOf', @expires_in OUT, 'expires_in'
    DECLARE @token_type nvarchar(4000)
    EXEC sp_OAMethod @json, 'StringOf', @token_type OUT, 'token_type'
    DECLARE @scope nvarchar(4000)
    EXEC sp_OAMethod @json, 'StringOf', @scope OUT, 'scope'

    EXEC @hr = sp_OADestroy @resp

    -- To use an access token in a MyInvois API call, see Using a MyInvois Access Token in an API Request

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @req
    EXEC @hr = sp_OADestroy @json


END
GO