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

EVEDEX Sub Account API

The SubAccount API from EVEDEX — 7 operation(s) for subaccount.

EVEDEX Sub Account API is one of 109 APIs that EVEDEX publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://auth-api.evedex.com.

7 operations 7 paths 10 schemas 2 GET2 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 3

EVEDEX Sub Account API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (InternalToken). It accepts HTTP bearer tokens (AccessToken). It accepts HTTP bearer tokens (RefreshToken).

Paths & Operations 7

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

SubAccount 7
PUT
/auth/sub-account/{id}
1 param body → 200
PUT
/auth/sub-account/{id}/unarchive
1 param → 200
POST
/auth/sub-account/switch
1 param body → 200
GET
/auth/sub-account/list
2 params → 200
POST
/auth/sub-account/create
1 param body → 200
GET
/auth/sub-account/{parentId}/{id}/check
3 params → 200
PUT
/auth/sub-account/{id}/archive
1 param → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are User (32 properties), SubAccount (11 properties), SmartAccountEntry (5 properties), SubAccountListResponse (5 properties). Each schema is shown below with its type and property counts.

JWT
object
JWT tokens
2 properties 1 required
SubAccountListResponse
object
5 properties 4 required
CreateSubAccountBody
object
4 properties 1 required
SwitchAccountBody
object
1 property 1 required
User
object
32 properties 30 required
Auth
object
Authorization payload
2 properties 2 required
SubAccountUpdateBody
object
1 property 1 required
SmartAccountEntry
object
5 properties 5 required
SubAccount
object
11 properties 11 required
EmptyResponse
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

evedex-subaccount-api-openapi.yml Raw ↑

Other APIs EVEDEX publishes across the network.

EVEDEX Documentation & Agent Surface
EVEDEX Async API (Centrifugo)
EVEDEX ACL API
EVEDEX AI Strategy API
EVEDEX Aml API
EVEDEX API Key API
EVEDEX Article API
EVEDEX Auth API
EVEDEX Badge API
EVEDEX Bill API
EVEDEX Blocked API
EVEDEX Bot API
Where this information came from

This is an independent, third-party profile of EVEDEX Sub Account 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.