The Spanish version is the authoritative reference. View in Spanish
Docupath: Docupath → Gosocket (manual contingency)
Gosocket exposes the UploadZipDocument endpoint to receive documents that Docupath has processed. Once the AI engine completes processing, Docupath packages the result (XML + original PDF) into a .zip and delivers it to Gosocket, which validates the package, registers the document and returns the processing status.
This flow only fires when the document reaches approved status in Docupath, which requires manual review in the portal — Docupath's auto-approval ("autoreview") feature doesn't behave reliably. That's why it isn't the integration's automatic mechanism: it's simply a manual contingency, useful for the cases where someone does approve the document by hand in the portal. The integration's real automatic process is Flow ③ — Periodic polling, which Gosocket runs on its own, without human intervention.
Process actors
Environments
| Environment | Endpoint URL |
|---|---|
| Sandbox (Testing) | https://systemintegrator-sbx.gosocket.net/api/v1/UploadZipDocument |
| Production | https://systemintegrator.gosocket.net/api/v1/UploadZipDocument |
Process flow
Step 1 — Authentication
HTTP Basic Auth with the credentials (Username + Password) that Gosocket assigns to Docupath, one per environment. The credentials go directly on every request; there is no token-issuing endpoint.
Step 2 — Prepare the ZIP
The .zip must meet these rules to be processed correctly:
Step 3 — Send the document
POST /api/v1/UploadZipDocument with a JSON body: country, externalId, batchId (the same values Gosocket sent in Flow ①, returned unchanged), fileBase64, fileExt="zip" and fileName. Gosocket registers the document, returns the data extracted from the XML (filesProcessed[]) and the isSuccess status.
They are the correlation keys for end-to-end tracking. Reusing a new UUID on a retry instead of the original ones breaks traceability.