Obtaining a Session Token/ID via API
To initiate the document upload process, it's essential to first acquire a unique session token or ID through our API. This session ID plays a crucial role in ensuring the integrity and organization of your uploaded documents.
Key Points:
1. Uniqueness of Session ID: Each document upload request must be accompanied by a unique session ID. This is vital to prevent accidental overwriting of documents.
2. Handling Multiple Documents: If the same session ID is reused for multiple documents, the most recently uploaded document will overwrite any previously uploaded document linked to that ID.
3. Flexibility with Document Types: Although each document requires a unique session ID, you can use the same session ID for uploading different types of documents. For instance, with session ID S1, you can upload a variety of documents such as payslips, employment certificates, and bank statements under this single ID.
Example Scenario:
- Session ID: S1:
- Document Type: Invoice
- Document Type: Payslip
- Document Type: Bank Statement
Remember, each session ID is a gateway for a set of different document types but is strictly singular for the same document type.
Implementation:
Ensure to generate a new session ID for each document of the same type to maintain the uniqueness and avoid data overlap.