How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

JustiFi Document API

Create/manage documents attached to your businesses and identities. When a document recordis created using this API the response object returns a presigned url used to upload thisdocument to an encrypted bucket. The presigned url can then be used to upload directly to anAWS s3 bucket, with a command like `curl -X PUT -T /path/to/file.pdf "insert presigned url"`.You must use the PUT method. This can also be accomplished from a backend or mobile app, from the browser or using our web components.After upload is complete the status changes from `pending` to `uploaded`.

JustiFi Document API is one of 28 APIs that JustiFi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Document. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 3 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.justifi.ai/v1.

3 operations 2 paths 4 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.justifi.ai/v1
Terms of Service
Resource Areas
1

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Document 3

Create/manage documents attached to your businesses and identities. When a document record is created using this API the response object returns a presigned url used to upload thi…

POST
/entities/document
Create a Document
CreateDocument 1 param body → 201
GET
/entities/document
List Documents
ListDocuments 1 param → 200
GET
/entities/document/{id}
Get a Document
GetDocument 2 params → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Document (12 properties), Envelope (4 properties), Envelope-list (4 properties), PageInfo (4 properties). Each schema is shown below with its type and property counts.

PageInfo
object
4 properties
Document
object
12 properties
Envelope-list
object
4 properties
Envelope
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

justifi-document-api-openapi.yml Raw ↑

Other APIs JustiFi publishes across the network.

JustiFi Ach Return Fees API
JustiFi Address API
JustiFi API Credentials API
JustiFi Balance Transactions API
JustiFi Bank Account API
JustiFi Bind Insurance API
JustiFi Business API
JustiFi Checkouts API
JustiFi Disputes API
JustiFi Fee Configurations API
JustiFi Identity API
JustiFi Payment Method Groups API
Where this information came from

This is an independent, third-party profile of JustiFi Document API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.