73 Strings Transaction API API
The Transaction APIs enable external enterprise customers to ingest and retrieve transaction ledger records within the 73 Strings platform.These APIs are intended for client-side engineering teams that manage their own data pipelines and require a controlled, structured interface to push transaction data into the platform or retrieve processed transaction information for downstream workflows.Key capabilitiesBulk creation and update of transaction ledger recordsPlatform-generated Display IDs for stable referencing across workflowsRetrieval of processed transaction dataReference APIs for transaction types and transaction versions to ensure payload correctnessPartial success handling for bulk ingestionAuthentication & data scopingAll APIs are authenticated using a subscription key associated with a User IDOrganization ID and User ID are mandatory in request payloads and determine data accessAPIs are multi-tenant by design and return data scoped to the provided organizationProcessing modelTransactions are pushed via external pipelines (real-time or batch)The platform persists and processes the data as per supported transaction structuresThe APIs do not orchestrate synchronization or enforce real-time guarantees
73 Strings Transaction API API is one of 6 APIs that 73 Strings publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Transaction API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 6 operations across 6 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against a single base URL, https://api-accord-eut-73strings.azure-api.net/transactions.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
73 Strings Transaction API API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as subscription-key (apiKeyHeader).
An API key is passed in the query as subscription-key (apiKeyQuery).
By default, every request must be authenticated, though some operations may also be called without credentials.
Paths & Operations 6
Across 6 paths, the API surfaces 6 operations — 6 POST. Each is listed below with its method, path, parameters, and response codes.
The Transaction APIs enable external enterprise customers to ingest and retrieve transaction ledger records within the 73 Strings platform . These APIs are intended for client-sid…
Schemas 29
The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are TransactionDto (38 properties), UnifiedTransactionData (17 properties), UnifiedTransactionV2Data (16 properties), MultilayeredTransactionMetadataResponse (16 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from 73 Strings 5
Other APIs 73 Strings publishes across the network.
This is an independent, third-party profile of 73 Strings Transaction API 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.