73 Strings · OpenAPI Overlay 1.0.0

API Evangelist enhancements for 73 Strings Transaction API

3 actions 3 updates update extends openapi/73-strings-transaction-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for 73 Strings's API. It is a proposal applied on top of the contract, not a document 73 Strings publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-providerx-apievangelist-profilex-spec-provenancex-conventionsx-error-catalogx-data-modelx-rate-limitsx-authentication

Targets 3

$.info
$
$.paths.*.*

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: API Evangelist enhancements for 73 Strings Transaction API
  version: 1.0.0
extends: openapi/73-strings-transaction-api-openapi.yml
x-generated: '2026-08-05'
x-method: generated
x-source: Assembled from the 73 Strings Azure API Management developer-portal Data API; enhancements derived from
  the repo artifacts.
actions:
- target: $.info
  update:
    x-apievangelist-provider: 73-strings
    x-apievangelist-profile: https://github.com/api-evangelist/73-strings
    x-spec-provenance: Harvested from https://api-accord-eut-73strings.developer.azure-api.net/developer/apis/transaction-api?api-version=2022-04-01-preview
      — the anonymous export returns paths:{}, so operations, parameters, request/response representations, examples
      and component schemas were assembled from the same portal Data API operations and schemas endpoints.
- target: $
  update:
    x-conventions: conventions/73-strings-conventions.yml
    x-error-catalog: errors/73-strings-problem-types.yml
    x-data-model: data-model/73-strings-data-model.yml
    x-rate-limits: rate-limits/73-strings-rate-limits.yml
    x-authentication: authentication/73-strings-authentication.yml
- target: $.paths.*.*
  update:
    x-error-envelope: Responses use the proprietary {response, success, message, errorCode} envelope. A business
      failure can arrive on HTTP 200 (errorCode EXCE00021). Read success/errorCode, not the HTTP status alone.
    x-idempotency: none — no idempotency key is supported on this API
    x-tenancy: orgId and userId are mandatory in the request body and scope all data access