Client Portal
File a Claim

Website Document Upload to ISi

Interactive walkthrough of the Insidea × COG ISi document-upload flow against the SBOA test API: authenticate, verify the JWT, validate claim details, then upload attachments.

API reference: SBOA API Docs

Insidea (site / API consumer) COG ISi (webhook / document endpoint)
Token ready —

1. Get Token Insidea

Exchange the Insidea test email + passKey for a persistent JWT. Token expiration is disabled — the token stays valid until replaced.

POST /getToken/index.cfm
Requesting token… 


				

					Testing tools (Insidea credentials)
					

						
						
						

						
					

				

			


			
			

				
2. Use Token ISi

				

					Verifies the JWT is present and valid in the system before protected
					operations. In production this is how subsequent API calls authenticate
					(token on every request). Here we call it explicitly so you can see the check.
				

				
POST /useToken/index.cfm  ·  header: token


				

				


				

					
					
—

				


				

					
					
				


				

					Verifying token…
				


				


				
			


			
			

				
3. Validate ID ISi Insidea

				

					Confirms Operator SBOA ID and Claim Number exist, are associated, and
					are active. On failure, show a message and do not unlock upload.
					On success, unlock the document uploader.
				

				
POST /validateID/index.cfm  ·  headers: token, ID, ClaimNumber


				

				


				

					
					
				


				

					
					
				


				

					
					
				


				

					Validating claim details…
				


				

			


			
			

				
4. Upload Attachments Insidea

				

					POST documents to the ISi Document Endpoint for the validated claim.
					Allowed: doc, docx, pdf, xls, xlsx, jpg, jpeg, gif, png.
					ISi then emails Email2Notes so the existing pipeline saves files and creates Diary Tasks.
				

				
POST /uploadClaimAttachments/index.cfm  ·  multipart field: attachments  ·  via WP proxy


				

				


				

				


				

					
					
				


				

					Uploading to ISi Document Endpoint…
				


				

			


		


		

			
How this maps to the Dev Build Plan

			
    
				
  1. SBOA Operator Login — operator reaches this upload experience (site login may wrap it).
    2. 
				
  2. Document Upload Landing — this page; upload stays locked until validation succeeds.
    3. 
				
  3. Validation Check — Get Token → Use Token → Validate ID (ISi webhook with token + SBOA ID + Claim Number).
    4. 
				
  4. Document Submission — Upload Claim Attachments multipart POST.
    5. 
				
  5. Backend Processing — ISi receives files and feeds Email2Notes → route/save + Diary Tasks.
    6. 
			

		


	






		
		

	
			

			

					

				

																														

		

				

					
Coming Soon

				

				

									We’re putting the finishing touches on this page.

This feature will be available soon.								

				

							

			
						
		

						

				

									
Thank you for your patience!