The XML-RPC interface is conceptually very similar to the REST interface. To make an XML-RPC request, you'll need to submit POST requests to the EpikTube XML-RPC endpoint:
Your XML-RPC request should have exactly one XML-RPC parameter of type "struct" that contains a field for every EpikTube API parameter. The only exception is the method name, which goes in the standard XML-RPC place (methodName). Here's the equivalent XML-RPC call for the example given in the "Getting Started" section of the API introduction page.
<methodCall>
<methodName>epiktube.users.get_profile</methodName>
<params>
<param><value><struct>
<member>
<name>user</name>
<value><string>EPIKTUBE_USER_NAME</string></value>
</member>
</struct></value></param>
</params>
</methodCall>
The XML-RPC response is a string that contains an escaped standalone XML document that contains the results of the API call. You may pass the XML document to your preferred XML parser to get parse the results. Here's an example XML-RPC result:
<methodResponse>
<params><param><value><string>
<?xml version="1.0" encoding="utf-8"?>
<ut_response status="ok">
<user_profile>
<first_name>EpikTube</first_name>
<last_name>User</last_name>
</user_profile>
</ut_response>
</string></value></param> </params>
</methodResponse>
Unescaping the XML response document will yield the same result as the response to a REST call. For ease-of-implementation, we highly recommend that you use an XML-RPC client library to handle the details of XML-RPC calls.
Copyright © 2025 EpikTube, Inc.
