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

nCino Transactions API

The Transactions API from nCino — 8 operation(s) for transactions.

nCino Transactions API is one of 86 APIs that nCino publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 9 operations across 8 paths, and defines 39 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://evault.ncino.com/api.

9 operations 8 paths 39 schemas 1 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.ncinomortgage.com
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

nCino Transactions API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • bearerAuth — JWT access token used to authorize every API request. Send it as Authorization: Bearer . Tokens are issued by the token endpoint (POST https://evault.ncino.com…
  • basicAuth — HTTP Basic credentials used only by the token endpoint (POST /oauth/authtoken). The username is your API clientid and the password is your clientsecret, sent a…

Paths & Operations 9

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

Transactions 9
GET
/{environment}/transactions/{transaction_id}
Get a transaction
getTransaction 2 params → 200401500
POST
/{environment}/transactions/{transaction_id}
Updates an existing transaction
2 params body → 200401500
POST
/{environment}/inquiry
Performs an inquiry
1 param body → 200401500
POST
/{environment}/connectivity
Performs a connectivity test
1 param body → 200401500
POST
/{environment}/enotes/{enote_id}/register
Performs a Registration
2 params body → 200401500
POST
/{environment}/enotes/{enote_id}/change-status
Performs a Change Status
2 params body → 200401500
POST
/{environment}/enotes/{enote_id}/change-data
Performs a Change Data
2 params body → 200401500
POST
/{environment}/enotes/{enote_id}/deliver
Performs a Delivery
2 params body → 200401500
POST
/{environment}/enotes/{enote_id}/transfer
Performs a Transfer
2 params body → 200401500

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are transaction_additional_details (25 properties), change_data_post (13 properties), transfer_post (11 properties), register_post (8 properties). Each schema is shown below with its type and property counts.

mers_response
string
is_system
boolean
general_iso8601
string
content_type
string
boolean
boolean
change_data_type
string
document_type
string
transaction_type
string
transfer_type
string
name
string
confirmation_type
string
change_status_post
object
2 properties 1 required
audit_logs
array
change_status_type
string
mers_org_id
string
guid
string
connectivity_post
object
1 property
detailed_transaction_type
string
event_type
string
status
string
incoming
boolean
min
string
is_test
boolean
modification_type
string
transfer_post
object
11 properties 2 required
inquiry_post
object
2 properties
default_success_response
object
3 properties
mers_address_type
string
transaction_post
object
1 property
effective_date
string
delivery_post
object
1 property 1 required
request_id
string
document_name
string
transfer_confirmation_status
string
change_data_post
object
13 properties 1 required
base64
string
delivery_recipient_status
string
register_post
object
8 properties 4 required
transaction_additional_details
object
25 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ncino-transactions-api-openapi.yml Raw ↑

Other APIs nCino publishes across the network.

nCino Mortgage MCP Servers
nCino Account Assignment Webhooks API
nCino Audit Logs API
nCino Authentication API
nCino Borrower Task Reminders API
nCino Borrowers API
nCino Branch Images API
nCino Branch Links API
nCino Branch Reports API
nCino Branch State Licenses API
nCino Companies API
nCino Company Images API
Where this information came from

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