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

AhaSend Sub Accounts API

Provision and manage isolated sub accounts under a parent account, their API keys, and their usage.

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

Tagged areas include Subaccounts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

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

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

13 operations 7 paths 15 schemas 2 DELETE5 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.ahasend.com
Authentication
HTTP Bearer
License
MIT
Resource Areas
1

Authentication & Security 1

AhaSend Sub Accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (aha-sk-64-CHARACTER-RANDOM-STRING) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — API key for authentication. Non-empty Security Requirement values are AhaSend API-key roles. Roles listed within one requirement object are jointly required; s…

Paths & Operations 13

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

Sub Accounts 13

Provision and manage isolated sub accounts under a parent account, including their API keys and usage.

GET
/v2/accounts/{account_id}/sub-accounts
List Sub Accounts
listSubAccounts 4 params → 200400401403404500
POST
/v2/accounts/{account_id}/sub-accounts
Create Sub Account
createSubAccount 2 params body → 201400401403404409422500
GET
/v2/accounts/{account_id}/sub-accounts/usage
Get Sub-Account Usage
getSubAccountsUsage 1 param → 200400401403404500
GET
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}
Get Sub Account
getSubAccount 2 params → 200400401403404500
PUT
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}
Update Sub Account
updateSubAccount 2 params body → 200400401403404500
DELETE
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}
Delete Sub Account
deleteSubAccount 2 params → 200400401403404500
POST
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/suspend
Suspend Sub Account
suspendSubAccount 2 params body → 200400401403404500
POST
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/unsuspend
Unsuspend Sub Account
unsuspendSubAccount 2 params → 200400401403404500
GET
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/api-keys
List Sub-Account API Keys
listSubAccountAPIKeys 5 params → 200400401403404500
POST
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/api-keys
Create Sub-Account API Key
createSubAccountAPIKey 3 params body → 201400401403404409422500
GET
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/api-keys/{key_id}
Get Sub-Account API Key
getSubAccountAPIKey 3 params → 200400401403404500
PUT
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/api-keys/{key_id}
Update Sub-Account API Key
updateSubAccountAPIKey 3 params body → 200400401403404500
DELETE
/v2/accounts/{account_id}/sub-accounts/{sub_account_id}/api-keys/{key_id}
Delete Sub-Account API Key
deleteSubAccountAPIKey 3 params → 200400401403404500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are SubAccount (11 properties), APIKey (10 properties), SubAccountUsageResponse (8 properties), APIKeyScope (6 properties). Each schema is shown below with its type and property counts.

APIKey
object
10 properties 10 required
APIKeyScope
object
6 properties 6 required
CreateAPIKeyRequest
object
3 properties 2 required
CreateSubAccountRequest
object
3 properties 2 required
ErrorResponse
object
Human-readable API error. The server currently sends no stable machine error code. In particular, clients must not parse message to distinguish IP-allow-list,…
1 property 1 required
PaginatedAPIKeysResponse
object
3 properties 3 required
PaginatedSubAccountsResponse
object
3 properties 3 required
PaginationInfo
object
3 properties 1 required
SubAccount
object
11 properties 11 required
SubAccountUsageBreakdown
object
4 properties 2 required
SubAccountUsageResponse
object
8 properties 8 required
SuccessResponse
object
1 property 1 required
SuspendSubAccountRequest
object
1 property 1 required
UpdateAPIKeyRequest
object
At least one non-null field must be provided, and at least one provided value must differ from the current value. Omitted or null fields are left unchanged.
3 properties
UpdateSubAccountRequest
object
At least one non-null field must be provided, and at least one provided value must differ from the current value. Omitted or null fields are left unchanged.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ahasend-sub-accounts-api-openapi.yml Raw ↑

Other APIs AhaSend publishes across the network.

AhaSend Accounts API
AhaSend API Keys API
AhaSend Domains API
AhaSend Email API
AhaSend Messages API
AhaSend Routes API
AhaSend SMTP Credentials API
AhaSend Statistics API
AhaSend Suppressions API
AhaSend Utility API
AhaSend Webhooks API
Where this information came from

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