Importing Data

Importing Data Using the XML API Import Tool


Bitfocus's RESTful XML API Import tool was developed to allow customers to programmatically access the Data Import Tool (DIT) and import HMIS data standards as well as custom fields. 

Required XML FY2024 Header For Data XML Files

<?xml version="1.0" encoding="UTF-8"?>
<hmis:Sources xmlns:airs="" xmlns:xsi="" xmlns:hmis="">

Required XML FY2024 Header For MAP XML Files

<?xml version="1.0" encoding="UTF-8"?>

<hmis:Sources xmlns:airs=""


Sending Import Requests

Your API username, password, and crypt key for any specific agency can be found in the Manage>Sharing section within Clarity Human Services under API Credentials. For more information, see API Credentials.


Non-working Example of PHP using CURL

$fullPathToXmlFile = 'Your-XML-File.xml';
$autUserName = 'YOUR-API-USER-KEY';
$autUserPassword = 'YOUR-API-USER-PASSWORD';
$apiUrl = '';
$client = new XmlImportClient($autUserName, $autUserPassword, $apiUrl);
$result = $client->importFile($fullPathToXmlFile);

class XmlImportClient {
* @var string full path to file being imported. File should not be encrypted!
protected $file;
* @var string HTTP auth user name
protected $username;
* @var string HTTP auth password.
protected $password;
* @var string url to target instance
protected $requestUrl;

public function __construct($username, $password, $requestUrl) {
$this->username = $username;
$this->password = $password;
$this->requestUrl = $requestUrl;

* Provides import of XML file to Clarity instance.
* @var string $file full path to file that should be imported.
* @return mixed import result.
public function importFile($file) {
$this->file = $file;

$request = $this->createRequest();

$result = $this->sendRequest($request);

return $result;

protected function createRequest() {
$request = curl_init();




return $request;

protected function initRequestTarget($request) {
$requestUrl = $this->requestUrl;
curl_setopt($request, CURLOPT_URL, $requestUrl);
curl_setopt($request, CURLOPT_TIMEOUT, 0);
curl_setopt($request, CURLOPT_RETURNTRANSFER, 1);

protected function attachFileToRequest($request) {
curl_setopt($request, CURLOPT_POST, true);
$dataFile = $this->file;
$fileName = basename($dataFile);
$fileType = 'text/xml';
$postData = array(
'data_file' => curl_file_create($dataFile, $fileType, $fileName), // Available since PHP 5.5
curl_setopt($request, CURLOPT_POSTFIELDS, $postData);

protected function attachAutInfoToRequest($request) {
curl_setopt($request, CURLOPT_USERPWD, $this->username . ':' . $this->password);
curl_setopt($request, CURLOPT_SSL_VERIFYPEER, 0);
curl_setopt($request, CURLOPT_SSL_VERIFYHOST, 0);

protected function attachImportPropertiesToRequest($request) {
curl_setopt($request, CURLOPT_HTTPHEADER, array(
'Standard-Version: 2020', // Indicates what standard to use
'Content-Encrypted: 0', // Indicates that data is not encrypted and MCrypt should not be used

protected function sendRequest($request) {
$result = curl_exec($request);
if (!$result) {
throw new Exception('Unable to receive response from the Clarity instance.');
return $result;


More Examples:

Visit our public Gitlab repo for more examples on how to use the DIT API.


Incoming XML Format

The incoming XML payload must conform to the conditions described in the HUD HMIS FY2024 Schema

 <hmis:Sources xmlns:hmis="" xmlns:xsi=""> 

XML 1.0 vs XML 1.1

While the official XML FY2024 specification calls for the use of XML 1.1, there are several issues we have run into with the adoption of XML 1.1 that have required us to create a local copy of the XSD, and make adjustments to make the XSD XML 1.0 compliant rather than XML 1.1 compliant. The key difference is that XML 1.1 allows the use of Assert expressions. These expressions allow dependency validation on specific fields. By removing these Assert dependency validations, the items become non-required, and we rely on proper XML FY2024 development to ensure that the dependencies are met.

Many programming frameworks do not include libraries that deal with XML 1.1.  This has caused significant issues with adoption of XML 1.1-based imports. Customers looking to import data were not able to use their native XML libraries and PHP-based libraries did not include support for XML 1.1. In order to make the XML FY2024 compliant with the standard XML 1.0, we made the XML FY2024 Schema XML 1.0 compliant by pointing the XSD to a local location, and adjusted the XSD to remove assets, such as the following:


  <!--Testing if DisabilityType is 8, before allowing use of TCellCountAvailable-->
<xs:assert test="if (hmis:TCellCountAvailable) then boolean(hmis:DisabilityType/text()='8') else true()"/>

<!--Testing if TCellCountAvailable is 1, before allowing use of TCellCount-->
<xs:assert test="if (hmis:TCellCountAvailable/text()='1') then boolean(hmis:TCellCount) else (if (not(hmis:TCellCountAvailable/text()='1')) then (not(boolean(hmis:TCellCount))) else false())"/>

<!--Testing if TCellCount is not null, before allowing use of TCellSource-->
<xs:assert test="if (hmis:TCellCount) then boolean(hmis:TCellSource) else (if (not(hmis:TCellCount)) then (not(boolean(hmis:TCellSource))) else false())"/>

<!--Testing if DisabilityType is 8, before allowing use of ViralLoadAvailable-->
<xs:assert test="if (hmis:ViralLoadAvailable) then boolean(hmis:DisabilityType/text()='8') else true()"/>

<!--Testing if ViralLoadAvailable is 1, before allowing use of ViralLoad-->
<xs:assert test="if (hmis:ViralLoadAvailable/text()='1') then boolean(hmis:ViralLoad) else (if (not(hmis:ViralLoadAvailable/text()='1')) then (not(boolean(hmis:ViralLoad))) else false())"/>

<!--Testing if ViralLoad is not null, before allowing use of ViralLoadSource-->
<xs:assert test="if (hmis:ViralLoad) then boolean(hmis:ViralLoadSource) else (if (not(hmis:ViralLoad)) then (not(boolean(hmis:ViralLoadSource))) else false())"/>

Clarity Human Services Mapping Document

To ensure mapping between source programs and services and the target Clarity Human Services Programs and Service Items, Clarity Human Services utilizes a mapping schema. Below is a sample XML file used to provide mapping. The YOUR-Organization-ID is a numeric ID only.

<?xml version="1.0"  encoding="UTF-8"?>
<map:Map xmlns:map="">
<ClarityID>677</ClarityID> // Target Clarity Program ID
<ExternalID>1</ExternalID> // Source System Program ID
<ClarityID>370</ClarityID> // Target Clarity Service Item ID
<ExternalID>583</ExternalID> //Source System Service iD


RESTful XML API Web Interface

There may be times you want to manually import your XML files. We provide a web interface that allows you to import your XML files once you have uploaded your mapping XML file.

RESTful Web URL  
File Status  
File Status URL:
Error Status  
Error Status URL
Import Results:  
Import Status URL:


The URLs above take you to one of three pages: Import Progress, Import Errors, and Import Results.






This XML response is generated every time a Mapping or Data XML file is imported into Clarity Human Services via the rest API.

This information will be provided to you by your system administrator. Please ensure you keep this information in a secure location as defined by your organization's security policies.

Organization ID Usage

It is important that you use the same Organization ID in your Data & Mapping XML documents. This ID is the unique key that ties your imported data and mapped programs and services to your agency.

Below are examples where the identifier needs to be consistently the same. In these examples, the Organization ID is "1234."

(1): XML Mapping File – SourceID


(2): XML Data File – SourceID


Error Messages

You may receive the following error messages:

<Category>program status</Category>
<Message>Client program status wasn't processed because client program was not found(Client program was probably not imported).</Message>
<Message>Client program exit wasn't processed because enrollment not found(Enrollment was probably not imported).</Message>

Possible Causes:

  • The enrollment wasn’t imported because program mappings weren’t configured for the enrollment program.
  • The enrollment hasn’t imported yet because of tag order in the input XML file (e.g., the “Exit” tag is located higher than the “Enrollment” tag). These messages must be located before the log message about enrollment, in this case.

Error Message

<Message>Client program enrollment wasn't processed because program with ID = "935" doesn't exist</Message>

Possible Causes:

  • The enrollment wasn’t imported because program mappings weren’t configured for the enrollment program.

Updated: 02/13/2024