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

Tratta Payment Methods API

Payment method storage and management

Tratta Payment Methods API is one of 10 APIs that Tratta publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Payment Methods. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 3 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version v1.0.0.

Requests are made against 2 base URLs: https://{org-uuid}.production.tratta.io/api/v1, https://{org-uuid}.sandbox.tratta.io/api/v1.

4 operations 2 paths 6 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0.0
Base URL
https://api.tratta.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tratta Payment Methods API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token provided by Tratta after organization setup

Paths & Operations 4

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

Payment Methods 4

Payment method storage and management

GET
/payment_methods
List Payment Methods
listPaymentMethods 2 params → 200
POST
/payment_methods
Create Payment Method
createPaymentMethod body → 201422
GET
/payment_methods/{id}
Get Payment Method
getPaymentMethod 1 param → 200404
DELETE
/payment_methods/{id}
Delete Payment Method
deletePaymentMethod 1 param → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PaymentMethod (7 properties), PaginationMeta (4 properties), PaymentMethodRequest (3 properties), PaymentMethodListResponse (2 properties). Each schema is shown below with its type and property counts.

PaymentMethodResponse
object
1 property
ErrorResponse
object
2 properties
PaymentMethodRequest
object
3 properties 2 required
PaginationMeta
object
4 properties
PaymentMethod
object
7 properties
PaymentMethodListResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tratta-payment-methods-api-openapi.yml Raw ↑

Other APIs Tratta publishes across the network.

Tratta Bulk Operations API
Tratta Charges API
Tratta Customer Sessions API
Tratta Customers API
Tratta Debt Accounts API
Tratta Payment Plans API
Tratta Tickets API
Tratta Transactions API
Tratta Webhooks API
Where this information came from

This is an independent, third-party profile of Tratta Payment Methods 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.