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

DoiT Billing Transfer API

Manage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts.

DoiT Billing Transfer API is one of 38 APIs that DoiT publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

8 operations 8 paths 29 schemas 6 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.doit.com
Authentication
API Key, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 3

DoiT Billing Transfer API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key). An API key is passed in the header as X-Tenant-Id (tenantId). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

  • api_key — Use the "Bearer " format or sign in for autofill
  • tenantId — Tenant (customer) ID that sets the request's customer context. Required when the credential can access more than one tenant; omit when the credential is scoped…

Paths & Operations 8

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

Billing Transfer 8

Manage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts.

POST
/billingtransfer/v1/resellerhandshakes
Create reseller handshakes (batch)
createBillingTransferResellerHandshakes 3 params body → 200400401403422500502
GET
/billingtransfer/v1/programmanagementaccounts
List program management accounts
listBillingTransferProgramManagementAccounts 3 params → 200400401403500
POST
/billingtransfer/v1/end-customer-mappings
Create end-customer mappings (batch)
createBillingTransferEndCustomerMappings 1 param body → 200400401403422500
GET
/billingtransfer/v1/programmanagementaccounts/status
Get program management account status
getBillingTransferProgramManagementAccountsStatus 1 param → 200400401403500
GET
/billingtransfer/v1/end-customers
List end-customers under a reseller PMA
listBillingTransferEndCustomers 4 params → 200400401403404500
GET
/billingtransfer/v1/resellers/{resellerPmaAccountId}/end-customers
List end-customers under a reseller PMA, by reseller PMA alone
listBillingTransferEndCustomersByReseller 3 params → 200400401403404500
GET
/billingtransfer/v1/reseller-accounts
List the caller's reseller PMA nodes
listBillingTransferResellerAccounts 1 param → 200400401403500
GET
/billingtransfer/v1/reseller-accounts/end-customers
List the caller's reseller PMA nodes with their end-customer tenants
listBillingTransferResellerAccountsWithTenants 2 params → 200400401403500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are ResellerAccountWithTenants (12 properties), ProgramManagementAccount (11 properties), EndCustomerNode (8 properties), MappedTenant (8 properties). Each schema is shown below with its type and property counts.

ResellerHandshakeBatchSummary
object
Per-outcome counts across the batch. Field names are snakecase, matching the actual wire format returned by this endpoint — an intentional inconsistency with t…
5 properties 5 required
ListResellerAccountsResponse
object
1 property 1 required
EndCustomerMappingBatchCreate
object
3 properties 3 required
EndCustomerMappingResultStatus
string
InvalidHandshakeItem
object
A single batch item that failed validation before processing began.
4 properties 2 required
HandshakeStatus
object
Per-AWS-Organizations-handshake-state counts across all tenants mapped to a PMA.
7 properties 7 required
ListEndCustomersResponse
object
1 property 1 required
Error
object
Standard error response structure.
1 property
ResellerHandshakeBatchCreate
object
3 properties 2 required
ProgramManagementAccountStatus
object
6 properties 4 required
BillingTransferProblemDetails
object
RFC 7807 problem-detail body returned by Billing Transfer endpoints for 4xx/5xx errors.
7 properties 4 required
EndCustomerMappingBatchResult
object
4 properties 3 required
ProgramManagementAccountsStatusResponse
object
1 property 1 required
IamDiff
object
2 properties
ResellerHandshakeItem
object
2 properties 2 required
ResellerAccountWithTenants
object
12 properties 10 required
ProgramManagementAccount
object
11 properties 9 required
MappedTenant
object
8 properties 7 required
EndCustomerNode
object
8 properties 6 required
EndCustomerMappingItem
object
3 properties 2 required
ResellerHandshakeBatchResult
object
3 properties 3 required
ResellerHandshakeResult
object
6 properties 3 required
ListResellerAccountsWithTenantsResponse
object
1 property 1 required
ResellerAccount
object
7 properties 6 required
ResellerHandshakeError
object
2 properties 2 required
ProgramManagementAccountList
object
3 properties 2 required
EndCustomerMappingResult
object
4 properties 3 required
ResellerHandshakeStatus
string
Outcome of processing this batch item.
HandshakeState
string
AWS Organizations Handshake State value, lowercased.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

doit-billing-transfer-api-openapi.yml Raw ↑

Other APIs DoiT publishes across the network.

DoiT MCP Server
DoiT Account Team API
DoiT Alerts API
DoiT Allocations API
DoiT Annotations API
DoiT Anomalies API
DoiT Assets API
DoiT Auth API
DoiT Ava API
DoiT Budget Suggestions API
DoiT Budgets API
DoiT Cloud Connect API
Where this information came from

This is an independent, third-party profile of DoiT Billing Transfer 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.