SQL Server
SQL Server
VoiceBase -- Upload a Media File with a JSON Configuration
See more VoiceBase Examples
This example uploads a media file and also provides a configuration file.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
DECLARE @iTmp0 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 assumes the Chilkat HTTP API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
-- Insert your Bearer token here:
DECLARE @accessToken nvarchar(4000)
SELECT @accessToken = 'VOICEBASE_TOKEN'
DECLARE @http int
EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
DECLARE @req int
EXEC @hr = sp_OACreate 'Chilkat.HttpRequest', @req OUT
EXEC sp_OASetProperty @req, 'HttpVerb', 'POST'
EXEC sp_OASetProperty @req, 'Path', '/v2-beta/media'
EXEC sp_OASetProperty @req, 'ContentType', 'multipart/form-data'
-- Add the access (bearer) token to the request, which is a header
-- having the following format:
-- Authorization: Bearer <userAccessToken>
DECLARE @sbAuth int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbAuth OUT
EXEC sp_OAMethod @sbAuth, 'Append', @success OUT, 'Bearer '
EXEC sp_OAMethod @sbAuth, 'Append', @success OUT, @accessToken
EXEC sp_OAMethod @sbAuth, 'GetAsString', @sTmp0 OUT
EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Authorization', @sTmp0
EXEC sp_OAMethod @req, 'AddFileForUpload2', @success OUT, 'media', 'qa_data/wav/msg_123_abc.wav', 'audio/x-wav'
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @req, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @http
EXEC @hr = sp_OADestroy @req
EXEC @hr = sp_OADestroy @sbAuth
RETURN
END
-- This is the JSON of the configuration to be added as a parameter to the upload:
-- (Obviously, if you want a callback, you would use a URL that goes to your own web server..)
-- {
-- "configuration":{
-- "publish":{
-- "callbacks":[
-- {
-- "url":"https://www.chilkatsoft.com/dss/update_vm_transcription.asp",
-- "method":"POST",
-- "include":[
-- "transcripts",
-- "keywords",
-- "topics",
-- "metadata"
-- ]
-- }
-- ]
-- },
-- "keywords":{
-- "groups":[]
-- }
-- }
-- }
-- This code produces the above JSON.
DECLARE @json int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'configuration.publish.callbacks[0].url', 'https://www.chilkatsoft.com/dss/update_vm_transcription.asp'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'configuration.publish.callbacks[0].method', 'POST'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'configuration.publish.callbacks[0].include[0]', 'transcripts'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'configuration.publish.callbacks[0].include[1]', 'keywords'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'configuration.publish.callbacks[0].include[2]', 'topics'
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'configuration.publish.callbacks[0].include[3]', 'metadata'
DECLARE @jConfig int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jConfig OUT
EXEC sp_OAMethod @json, 'ObjectOf2', @success OUT, 'configuration', @jConfig
DECLARE @jKeywords int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jKeywords OUT
EXEC sp_OAMethod @jConfig, 'AppendObject2', @success OUT, 'keywords', @jKeywords
DECLARE @jGroups int
EXEC @hr = sp_OACreate 'Chilkat.JsonArray', @jGroups OUT
EXEC sp_OAMethod @jKeywords, 'AppendArray2', @success OUT, 'groups', @jGroups
-- Add the configuration JSON to the upload.
EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
EXEC sp_OAMethod @req, 'AddParam', NULL, 'configuration', @sTmp0
-- Do the upload..
DECLARE @resp int
EXEC @hr = sp_OACreate 'Chilkat.HttpResponse', @resp OUT
EXEC sp_OAMethod @http, 'HttpSReq', @success OUT, 'apis.voicebase.com', 443, 1, @req, @resp
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @http
EXEC @hr = sp_OADestroy @req
EXEC @hr = sp_OADestroy @sbAuth
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @jConfig
EXEC @hr = sp_OADestroy @jKeywords
EXEC @hr = sp_OADestroy @jGroups
EXEC @hr = sp_OADestroy @resp
RETURN
END
-- Examine the response status code and body.
EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
PRINT 'Response status code = ' + @iTmp0
-- The response should be JSON, even if an error.
EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
EXEC sp_OAMethod @json, 'Load', @success OUT, @sTmp0
EXEC sp_OASetProperty @json, 'EmitCompact', 0
EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
PRINT @sTmp0
-- A successful response will have a status code = 200
EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
IF @iTmp0 <> 200
BEGIN
PRINT 'Failed.'
END
ELSE
BEGIN
EXEC sp_OAMethod @json, 'StringOf', @sTmp0 OUT, 'mediaId'
PRINT 'mediaId: ' + @sTmp0
EXEC sp_OAMethod @json, 'StringOf', @sTmp0 OUT, '_links.self.href'
PRINT 'href: ' + @sTmp0
EXEC sp_OAMethod @json, 'StringOf', @sTmp0 OUT, 'status'
PRINT 'status: ' + @sTmp0
PRINT 'Success.'
END
-- Here is an example of a successful response:
-- {
-- "_links": {
-- "self": {
-- "href": "/v2-beta/media/856a1e85-c847-4c3c-b7a4-6cf15cd51db4"
-- }
-- },
-- "mediaId": "856a1e85-c847-4c3c-b7a4-6cf15cd51db4",
-- "status": "accepted",
-- "metadata": {}
--
EXEC @hr = sp_OADestroy @http
EXEC @hr = sp_OADestroy @req
EXEC @hr = sp_OADestroy @sbAuth
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @jConfig
EXEC @hr = sp_OADestroy @jKeywords
EXEC @hr = sp_OADestroy @jGroups
EXEC @hr = sp_OADestroy @resp
END
GO