BY NUMBER7 AIPRODUCT / DOCUMENT & INVOICE API
Turn documents into structured results your application can use.
Submit a file or supported document URL, retain the returned job ID, then retrieve structured results through polling or the documented webhook. Your application owns downstream review, approval and action.
A document job your application can follow.
NUMBER7 API · ASYNC JOBLIVE CONTRACT
{
"jobId": "job_7f92",
"fileStatus": "done",
"result": { "documentType": "invoice" }
}NUMBER7 APIstructured document resultYOUR APPLICATIONreview · approval · action
Submit the document
Authenticate and send a file or supported document URL.
Inspect stage records
REQUESTBearer-token authenticationRequired
DOCUMENTFile or URLSubmit
CONTEXTSupported document typeSpecify
Track asynchronous processing
Keep the returned job identifier in your application.
Inspect stage records
JOB IDReturned for trackingRetain
STATUSProcessing is asynchronousPending
CLIENTAvoid assuming immediate completionWait
Retrieve the structured result
Use polling or the documented webhook contract.
Inspect stage records
POLLRequest job status and resultsRetrieve
WEBHOOKReceive configured notificationNotify
ERRORHandle documented failure statesInspect
Keep your business controls explicit
Extraction output enters your application’s workflow.
Inspect stage records
RESULTStructured document valuesUse
REVIEWUncertain or failed casesRoute
APPOwn downstream approval and actionControl
Select a stage to pause and inspect the detail.
ACTUAL DOCUMENT API CONTRACT
Make the first request. Track the job. Retrieve the result.
The request and result states below follow the published Number7 API contract.
POST /api/v1/upload
?document.type=invoice&document.version=v1
multipart: file + fileName + fileTypedata.jobId
fileStatus: processingGET /api/v1/results/{jobId}
fileStatus: done | failedReturns the documented structured result and status.
Owns downstream review, approval and action unless separately implemented.
THE BUILD DECISION
Do not build the financial control layer twice.
Use AIdaptIQ for document-family assembly, typed transaction state, evidence and controls; keep your product experience and downstream systems yours.
01 / CONTRACT
Asynchronous by design.
Large document families and human resolution are lifecycle state, not request latency.
Create
File, URL, email or batch starts an idempotent job.
Observe
Polling and signed events expose canonical state.
Inspect
Typed results include evidence and control outcomes.
Resolve
Permitted actions update and replay the transaction.
Export
Downstream outcome returns to the same state.
02 / PLATFORM SURFACE
Infrastructure your application can depend on.
Versioned contracts and explicit failure behavior.
File or URL
Create jobs from files, URLs or email.
Typed results
Headers, lines, raw text and evidence.
Signed webhooks
Reliable state transitions.
Idempotency
Safe ingestion and export retries.
Document families
Invoice, PO, GRN, credit note and more.
Developer contracts
OpenAPI, Postman, errors and changelog.
NEXT STEP
Review the integration contract.
Map the API lifecycle, result schema and downstream action with our product team.