Developer reference · v1

API contract availability

Check the published v1 guidance and the availability of verified OpenAPI and Postman resources.

Published contract guidance · Reviewed 8 September 2026

OpenAPI and Postman availability.

OpenAPI specificationNot published
Postman collectionNot published

A downloadable verified OpenAPI contract and Postman collection are not supplied on this site. They require a verified specification from the API owner.

The published upload, result lookup and webhook guidance is available in the quickstart and reference chapters.

The published contract checkpoints.

CheckpointPublished guidance
Base URLhttps://api.number7ai.com/api/v1
UploadPOST /upload with document type/version query parameters and multipart fields
Result lookupGET /results/{jobId}
AuthenticationBearer token
Identifierdata.jobId
Completion statusdata.fileStatus

Validate the contract for your integration.

  1. Use one non-sensitive test document and a restricted development key.
  2. Confirm response fields, document limits, timeout behavior and webhook verification.
  3. Keep credentials out of source control and exported collections.
  4. Use the actual agreed schema when building a result consumer.

Discuss contract and access requirements

Scope and action

Agree what proceeds and what needs approval.

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.

Contract and test access

Request the verified integration materials.

No validated OpenAPI file or Postman collection is included in this website repository. The existing upload, result and webhook examples are published guidance; they have not been verified here against a production gateway or a credentialed test account.

Before implementing a consumer, confirm the released response schema, authentication, error envelope, rate and size limits, webhook signature and delivery semantics, retention, versioning and test environment.

Request API contract and test access
Discuss API integration→