Merge
OpenAPI V2
Was this helpful?
OpenAPI V2
Was this helpful?
Render two XBRL reports and merge them into one new XBRL report (.xbrl) and a log with not merged content is available. For each of the functionality where in our API is produced result file we produce hash of the file that identifies the contents of the file. User can validate the hash value in hash validation functionality and to know if any changes are applied. By default the file hash is disabled, but it can be controlled from the dropdown below. Response body will be for example:
{
"MergedContent": "JVBERxLjQKMSAw...",
"UnmergedContent": "GdsWdcdxDsaFgSd...",
"hashResult": {
"Hash_Result": "nKDBo115PBhw3U3Y= "
}
}
Specifies whether to have a hashcode included in the output. By default the value is false.
falseName of the application to integrates with API’s to Semansys.Next.
Contract owner (organization) name that have embedded the API’s.
Business Identification Number (BIN) of the contract owner (organization) to embeds the API’s.
Customer (organization) name (ie. accounting firm, intermediary, ....).
Business Identification Number (BIN) of the customer.
Client (organization) name of the customer of the accounting firm, intermediary...
Business Identification Number (BIN) of the client.
The main and child files that are going to be merged.
{"master":"base64 content","child":"base64 content"}