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

Fincura Files API

Files serve as the source input data for our insights engine. They are represented by a `DocumentFile` record.

Fincura Files API is one of 20 APIs that Fincura publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include File. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 6 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.0.2, at version 1.3.1.

Requests are made against the base URL https://api.fincura.com.

6 operations 4 paths 4 schemas 1 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.3.1
Base URL
https://api.fincura.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Fincura Files API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (API_Key). By default, every request must be authenticated.

Paths & Operations 6

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

Files 6

Files serve as the source input data for our insights engine. They are represented by a DocumentFile record.

GET
/v1/document-file
List DocumentFile records
listDocumentFiles 3 params → 200
POST
/v1/document-file
Submit a new DocumentFile
createDocumentFile body → 201429
GET
/v1/document-file/{uuid}
Get a DocumentFile
retrieveDocumentFile 2 params → 200
DELETE
/v1/document-file/{uuid}
Delete a DocumentFile
destroyDocumentFile 2 params → 204
GET
/v1/bulk-file/{uuid}
Retrieve a BulkFile
retrieveBulkFile 1 param → 200
POST
/v1/bulk-file
Submit a new BulkFile
createBulkFile body → 201

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are DocumentFileRead (15 properties), DocumentFileCreate (11 properties), BulkFileRead (9 properties), BulkFileCreate (9 properties). Each schema is shown below with its type and property counts.

BulkFileCreate
object
9 properties 1 required
DocumentFileCreate
object
11 properties 2 required
DocumentFileRead
object
15 properties 1 required
BulkFileRead
object
9 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fincura-files-api-openapi.yml Raw ↑

Other APIs Fincura publishes across the network.

Fincura Api-Key API
Fincura Borrowers API
Fincura CustomAttributes API
Fincura DataViews API
Fincura DscrAnalysis API
Fincura DscrTemplate API
Fincura EmbeddedDocument API
Fincura EmbeddedDscrAnalysis API
Fincura EmbeddedFinancials API
Fincura EmbeddedGlobalCashflowAnalysis API
Fincura FinancialStatementSubmission API
Fincura GlobalCashflowAnalysis API
Where this information came from

This is an independent, third-party profile of Fincura Files 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.