Which statement is NOT true for the Archer APIs?

According to the Archer API Guide and Administration II materials, the Archer APIs have specific formatting requirements based on their architecture. The SOAP API (Simple Object Access Protocol) is strictly bound to the XML-based SOAP protocol. It uses a Web Services Description Language (WSDL) to define the structure of its messages, and these messages must be formatted as XML . It cannot process or return JSON payloads.

In contrast, the RESTful API is more flexible; while it defaults to JSON for modern integrations, it is capable of supporting both XML and JSON depending on the "Content-Type" and "Accept" headers provided in the request. The Content API , which is a specific subset of the Archer RESTful infrastructure, also follows these multi-format capabilities. Therefore, the statement that the SOAP API can use JSON is the incorrect one. For administrators building integrations, understanding this distinction is vital, as modern web applications typically prefer JSON, but legacy Archer SOAP services will reject any request that is not valid XML.