Invoice API documentation

One invoice. One job ID. A result your application can use.

Integrate invoice extraction and document processing through the Number7 AI API. Upload a document, retain its job ID and retrieve the structured result by polling or a signed completion webhook.

01 · SubmitFile or supported URLPOST /upload
02 · TrackRetain the job IDdata.jobId
03 · RetrieveRead completion statusdata.fileStatus
04 · UseYour application decidesReview · approval · action

The documented API returns document data and processing state. A completed job does not establish vendor validity, approval, posting or payment.

The first request uses multipart upload.

Use the published invoice type and v1 query parameters. Persist data.jobId from the response before you begin polling.

Invoice upload · cURL
curl --fail-with-body --request POST \
  'https://api.number7ai.com/api/v1/upload?document.type=invoice&document.version=v1' \
  --header "Authorization: Bearer $N7_API_KEY" \
  --form 'file=@invoice.pdf' \
  --form 'fileName=invoice.pdf' \
  --form 'fileType=application/pdf'

Follow the result lookup

Keep the integration boundary visible.

Number7 AI API

Process the document

Accept a supported source, process it asynchronously and return the documented result and status.

Your application

Own the business workflow

Apply required fields, client context, review, approval and downstream action. Retain the original source and job identifier.

Explore the document APIExplore the full AP workflow

Public examples follow the published v1 document flow. Confirm the response schema and operational limits for your account before implementation.

Check contract availability

Scope and action

Agree what proceeds and what needs approval.

Confirm deployment scope

Invoice capture and mixed PDF splitting

Read invoices and keep each vendor bill connected to its original source pages. Confirm the supported document mix for your implementation.

Action: Automatic with review.

Read the workflow scope
Confirm deployment scope

API access and customer-hosted deployment

Request the verified integration contract and hosting scope. Public guidance is not a validated machine-readable specification or a promise of SDK availability.

Action: Scope agreement required.

Read the workflow scope

The recorded product-owner confirmation applies to the named capabilities. Deployment scope, integration permissions and approval requirements are agreed separately.

The examples below are published integration guidance. Check verified contract availability before relying on account-specific schemas or limits.

Discuss API integration→