Currency Layer
Interact with currencylayer API using SQL Server
- Install the SQLHTTP database on your SQL Server
- Obtain an API Key from currencylayer
- Create the stored procedures documented below
- Execute the following SQL statement:
1 2 3 |
EXEC usp_APILayer_Auth_Init @APIKey = 'enter your api key' |
1 2 3 4 5 6 7 |
CREATE PROCEDURE usp_APILayer_Auth_Init(@APIKey varchar(35)) AS EXEC SQLHTTP.net.AuthParamSet @Profile = 'apilayer', @Name = 'APIKey', @Value = @APIKey GO |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 |
CREATE PROCEDURE usp_APILayer_Fetch( @Type varchar(10), @Parameters varchar(20), @Response nvarchar(MAX) OUTPUT, @StatusCode int OUTPUT, @StatusDescription nvarchar(MAX) OUTPUT) AS IF LOWER(@Type) NOT IN ('historical', 'live') BEGIN RAISERROR('Invalid @Type parameter', 16, 1) RETURN END DECLARE @URL nvarchar(MAX) DECLARE @QueryString nvarchar(MAX) DECLARE @HTTPSessionID uniqueidentifier SET @URL = 'http://apilayer.net/api' EXEC SQLHTTP.net.UrlBuilder @URL OUTPUT, 'apilayer', @Type IF @Type = 'historical' EXEC SQLHTTP.net.QueryStringBuilder @QueryString OUTPUT, 'apilayer', 'access_key', '#APIKey', 'date', @Parameters ELSE EXEC SQLHTTP.net.QueryStringBuilder @QueryString OUTPUT, 'apilayer', 'access_key', '#APIKey', 'currencies', @Parameters SET @URL = @URL + @QueryString EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT EXEC SQLHTTP.net.HTTPRequest @HttpSessionID, @URL = @URL, @Method = 'GET', @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT, @Response = @Response OUTPUT GO |
IMPORTANT DISCLAIMER
CODE/SQL ON THESE PAGES ARE PROVIDED AS-IS AND ARE AVAILABLE FOR ILLUSTRATIVE PURPOSES ONLY.
USERS ARE REQUIRED TO ABIDE BY THE TERMS AND CONDITIONS FOR USING REFERENCED THIRD PARTY WEBSITES AND/OR APIs FROM THEIR RESPECTIVE WEBSITES. WE DO NOT CONDONE ANY VIOLATION OF THIRD PARTY WEBSITES AND/OR APIs TERMS AND CONDITIONS USING OUR SOFTWARE.
USERS SHALL BE SOLELY RESPONSIBLE AND BE SOLELY LIABLE FOR VIOLATION OF ANY RULES SPECIFIED BY THIRD PARTIES FOR USING THEIR WEBSITES AND/OR APIs, OR INFRINGEMENT OF RIGHTS OF SUCH THIRD PARTIES.