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

Salt Edge Customers API

The Customers API from Salt Edge — 2 operation(s) for customers.

Salt Edge Customers API is one of 13 APIs that Salt Edge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version v5.

Requests are made against a single base URL, https://www.saltedge.com/api/v5.

3 operations 2 paths 3 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v5
Base URL
https://www.saltedge.com/api/v5
Authentication
API Key, API Key, API Key, API Key
Contact
Resource Areas
1

Authentication & Security 4

Salt Edge Customers API declares 4 security schemes for authenticating requests. An API key is passed in the header as App-id (appId). An API key is passed in the header as Secret (secret). An API key is passed in the header as Signature (signature). An API key is passed in the header as Expires-at (expiresAt). By default, every request must be authenticated.

  • appId — Salt Edge application identifier.
  • secret — Salt Edge application secret key.
  • signature — Base64-encoded SHA256 RSA signature (required in live mode).
  • expiresAt — Unix-timestamp request expiration (required in live mode).

Paths & Operations 3

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

Customers 3
GET
/customers
List or retrieve customers
listCustomers 3 params → 200
POST
/customers
Create a customer
createCustomer body → 200
DELETE
/customers/{id}
Remove a customer
removeCustomer 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Customer (6 properties), CustomerList (2 properties), CustomerResponse (1 property). Each schema is shown below with its type and property counts.

CustomerResponse
object
1 property
CustomerList
object
2 properties
Customer
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

salt-edge-customers-api-openapi.yml Raw ↑

Other APIs Salt Edge publishes across the network.

Salt Edge Account Information API
Salt Edge Payment Initiation API
Salt Edge Partners (Compliance Solution) API
Salt Edge Data Enrichment API
Salt Edge Accounts API
Salt Edge Connect Sessions API
Salt Edge Connections API
Salt Edge Consents API
Salt Edge Countries API
Salt Edge Holder Info API
Salt Edge Providers API
Salt Edge Transactions API
Where this information came from

This is an independent, third-party profile of Salt Edge Customers 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.