Account Settings - Fetch

Retrieve Twitter account settings using SQL Server

Prerequisites:

See SQLHTTP easy setup for Twitter
See API Call documentation for parameter values and other information
Create the stored procedure documented below

Stored Procedure:


CREATE PROCEDURE usp_Twitter_Account_Settings_Fetch(
		@Profile nvarchar(100),
		@Response nvarchar(MAX) OUTPUT,
		@StatusCode int OUTPUT,
		@StatusDescription nvarchar(MAX) OUTPUT)

AS
 
DECLARE @URL nvarchar(MAX)
DECLARE @HTTPSessionID uniqueidentifier

SET @URL = 'https://api.twitter.com/1.1/account/settings.json'

EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT

EXEC usp_Twitter_Auth_Header @Profile, @HTTPSessionID, @URL, 'GET'

EXEC SQLHTTP.net.HTTPRequest    @HttpSessionID, 
				@URL = @URL,
				@Method = 'GET',
				@ContentType = 'application/json',
				@Accept = 'application/json',
				@StatusCode = @StatusCode OUTPUT,
				@StatusDescription = @StatusDescription OUTPUT,
				@Response = @Response OUTPUT
GO

CREATE PROCEDURE usp_Twitter_Account_Settings_Fetch(

@Profile nvarchar(100),

@Response nvarchar(MAX) OUTPUT,

@StatusCode int OUTPUT,

@StatusDescription nvarchar(MAX) OUTPUT)

DECLARE @URL nvarchar(MAX)

DECLARE @HTTPSessionID uniqueidentifier

SET @URL = 'https://api.twitter.com/1.1/account/settings.json'

EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT

EXEC usp_Twitter_Auth_Header @Profile, @HTTPSessionID, @URL, 'GET'

EXEC SQLHTTP.net.HTTPRequest @HttpSessionID,

@URL = @URL,

@Method = 'GET',

@ContentType = 'application/json',

@Accept = 'application/json',

@StatusCode = @StatusCode OUTPUT,

@StatusDescription = @StatusDescription OUTPUT,

@Response = @Response OUTPUT



Sample Usage:


DECLARE @Response nvarchar(MAX)
DECLARE @StatusCode int
DECLARE @StatusDescription nvarchar(MAX)

EXEC usp_Twitter_Account_Settings_Fetch
		@Profile = 'My Twitter',	
		@Response = @Response OUTPUT, 
		@StatusCode = @StatusCode OUTPUT, 
		@StatusDescription = @StatusDescription OUTPUT

IF @StatusCode >= 400
	EXEC SQLHTTP.net.RaiseHttpError @StatusCode, @StatusDescription, @Response
ELSE
	BEGIN

		DECLARE @X xml
		SET @X = SQLHTTP.net.Json_To_Xml(@Response, '0')

		--The XPath syntax below was easily generated by executing the following commands:
		--EXEC SQLHTTP.net.XQueryHelper @X
		--and then executing: 
		--EXEC SQLHTTP.net.XQueryHelper @X, 'JsonObject'

		SELECT T.C.value(N'@discoverable_by_email', N'nvarchar(MAX)') AS [discoverable_by_email]
		      ,T.C.value(N'@language', N'nvarchar(MAX)') AS [language]
		      ,T.C.value(N'@geo_enabled', N'nvarchar(MAX)') AS [geo_enabled]
		      ,T.C.value(N'@screen_name', N'nvarchar(MAX)') AS [screen_name]
		      ,T.C.value(N'sleep_time[1]/@enabled', N'nvarchar(MAX)') AS [sleep_time_enabled]
		FROM @X.nodes(N'/JsonObject') T(C)

	END

DECLARE @Response nvarchar(MAX)

DECLARE @StatusCode int

DECLARE @StatusDescription nvarchar(MAX)

EXEC usp_Twitter_Account_Settings_Fetch

@Profile = 'My Twitter',

@Response = @Response OUTPUT,

@StatusCode = @StatusCode OUTPUT,

@StatusDescription = @StatusDescription OUTPUT

IF @StatusCode >= 400

EXEC SQLHTTP.net.RaiseHttpError @StatusCode, @StatusDescription, @Response

ELSE

BEGIN

DECLARE @X xml

SET @X = SQLHTTP.net.Json_To_Xml(@Response, '0')

--The XPath syntax below was easily generated by executing the following commands:

--EXEC SQLHTTP.net.XQueryHelper @X

--and then executing:

--EXEC SQLHTTP.net.XQueryHelper @X, 'JsonObject'

SELECT T.C.value(N'@discoverable_by_email', N'nvarchar(MAX)') AS [discoverable_by_email]

,T.C.value(N'@language', N'nvarchar(MAX)') AS [language]

,T.C.value(N'@geo_enabled', N'nvarchar(MAX)') AS [geo_enabled]

,T.C.value(N'@screen_name', N'nvarchar(MAX)') AS [screen_name]

,T.C.value(N'sleep_time[1]/@enabled', N'nvarchar(MAX)') AS [sleep_time_enabled]

FROM @X.nodes(N'/JsonObject') T(C)

END

discoverable_by_email language geo_enabled screen_name sleep_time_enabled

--------------------- ---------- ------------ ------------- -------------------

true en false theSeanCook false



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.