Tags - Fetch
Retrieve WordPress Tags using SQL Server
- See SQLHTTP easy setup for WordPress
- See API Call documentation for parameter values and other information
- Create the stored procedure documented below
|
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 49 50 51 52 53 54 55 56 57 58 59 60 61 |
CREATE PROCEDURE usp_WordPress_v2_Tags_Fetch( @Profile nvarchar(100), @context varchar(10) = 'view', @page int = 1, @per_page int = 10, @search varchar(100) = NULL, @exclude int = NULL, @include int = NULL, @offset int = NULL, @order varchar(10) = 'asc', @orderby varchar(20) = 'name', @slug varchar(100) = NULL, @post int = NULL, @hide_empty varchar(5) = NULL, @Response nvarchar(MAX) OUTPUT, @StatusCode int OUTPUT, @StatusDescription nvarchar(MAX) OUTPUT) AS DECLARE @URL nvarchar(MAX) DECLARE @QueryString nvarchar(MAX) DECLARE @HTTPSessionID uniqueidentifier SET @URL = SQLHTTP.net.AuthParam(@Profile, 'RootURL') EXEC SQLHTTP.net.UrlBuilder @URL OUTPUT, @Profile, 'wp-json', 'wp', 'v2', 'tags' EXEC SQLHTTP.net.QueryStringBuilder @QueryString OUTPUT, @Profile, 'context', @context, 'page', @page, 'per_page', @per_page, 'search', @search, 'exclude', @exclude, 'include', @include, 'offset', @offset, 'order', @order, 'orderby', @orderby, 'slug', @slug, 'post', @post, 'hide_empty', @hide_empty SET @URL = @URL + @QueryString EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT EXEC usp_WordPress_v2_Auth_Header @HTTPSessionID, @Profile, @URL, 'GET' EXEC SQLHTTP.net.HTTPRequest @HttpSessionID, @URL = @URL, @Method = 'GET', @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT, @Response = @Response OUTPUT 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 |
DECLARE @Response nvarchar(MAX) DECLARE @StatusCode int DECLARE @StatusDescription nvarchar(MAX) EXEC usp_WordPress_v2_Tags_Fetch @Profile = 'My Website', @context = 'edit', @per_page = 20, @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, 'JsonArray/JsonObject' SELECT T.C.value(N'@id', N'nvarchar(MAX)') AS [id] ,T.C.value(N'@name', N'nvarchar(MAX)') AS [name] ,T.C.value(N'@slug', N'nvarchar(MAX)') AS [slug] ,T.C.value(N'@taxonomy', N'nvarchar(MAX)') AS [taxonomy] ,T.C.value(N'@description', N'nvarchar(MAX)') AS [description] FROM @X.nodes(N'/JsonArray/JsonObject') T(C) END |
|
1 2 3 4 5 6 |
id name slug taxonomy description ------- ------------- ------------ ---------- ------------------------ 17 Updated Tag new-tag post_tag This is an updated tag 9 First Tag first-tag post-tag First Tag |
- Categories – Fetch
- Category – Create
- Category – Delete
- Category – Fetch
- Category – Update
- Comment – Create
- Comment – Delete
- Comment – Fetch
- Comment – Update
- Comments – Fetch
- Media – Delete
- Media – Download
- Media – Fetch
- Media – Update
- Media – Upload
- Media Item – Fetch
- Page – Create
- Page – Delete
- Page – Fetch
- Page – Update
- Pages – Fetch
- Post – Create
- Post – Delete
- Post – Fetch
- Post – Update
- Post Type – Fetch
- Posts – Fetch
- Settings – Update
- Status – Fetch
- Statuses – Fetch
- Tag – Create
- Tag – Delete
- Tag – Fetch
- Tag – Update
- Tags – Fetch
- Taxonomies – Fetch
- Taxonomy – Fetch
- Types – Fetch
- User – Create
- User – Delete
- User – Fetch
- User – Update
- Users – Fetch
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.