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

Dfns Approvals API

Approval workflow driven by the policy engine.

Dfns Approvals API is one of 12 APIs that Dfns publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 3 paths, and defines 1 schema. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api.dfns.io, https://api.uae.dfns.io.

3 operations 3 paths 1 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.dfns.io
Authentication
HTTP Bearer, API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Dfns Approvals API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the header as X-DFNS-APPID (AppId). An API key is passed in the header as X-DFNS-USERACTION (UserAction). By default, every request must be authenticated.

  • BearerAuth — Access token issued to a service account or a logged-in user. Sent as Authorization: Bearer .
  • AppId — The Dfns application (app) id the request is made on behalf of.
  • UserAction — A User Action Signature token proving the caller cryptographically signed the request payload. Required on sensitive mutating operations (transfers, signature…

Paths & Operations 3

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

Approvals 3

Approval workflow driven by the policy engine.

GET
/v2/policy-approvals
List approvals
listApprovals → 200
GET
/v2/policy-approvals/{approvalId}
Get an approval by id
getApproval 1 param → 200
POST
/v2/policy-approvals/{approvalId}/decisions
Create an approval decision (approve or deny)
createApprovalDecision 1 param body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Approval (4 properties). Each schema is shown below with its type and property counts.

Approval
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dfns-approvals-api-openapi.yml Raw ↑

Other APIs Dfns publishes across the network.

Dfns Auth API
Dfns Keys API
Dfns Networks API
Dfns Permissions API
Dfns Policies API
Dfns ServiceAccounts API
Dfns Signatures API
Dfns Transactions API
Dfns Transfers API
Dfns Wallets API
Dfns Webhooks API
Where this information came from

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