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

MX Technologies transaction rules API

The transaction rules API from MX Technologies — 2 operation(s) for transaction rules.

MX Technologies transaction rules API is one of 31 APIs that MX Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Transaction_rules. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 4 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.0.0, at version 20111101.

Requests are made against 2 base URLs: https://int-api.mx.com, https://api.mx.com.

4 operations 2 paths 8 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
20111101
Base URL
https://api.mx.com
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

MX Technologies transaction rules API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 4

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

transaction rules 4
GET
/users/{user_guid}/transaction_rules
List transaction rules
listTransactionRules 3 params → 200
POST
/users/{user_guid}/transaction_rules
Create transaction rule
createTransactionRule 1 param body → 200
GET
/users/{user_guid}/transaction_rules/{transaction_rule_guid}
Read transaction rule
readTransactionRule 2 params → 200
PUT
/users/{user_guid}/transaction_rules/{transaction_rule_guid}
Update transaction rule
updateTransactionRule 2 params body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are TransactionRuleResponse (7 properties), PaginationResponse (4 properties), TransactionRuleUpdateRequest (3 properties), TransactionRuleCreateRequest (3 properties). Each schema is shown below with its type and property counts.

TransactionRuleResponse
object
7 properties
TransactionRuleUpdateRequest
object
3 properties
TransactionRuleUpdateRequestBody
object
1 property
PaginationResponse
object
4 properties
TransactionRuleResponseBody
object
1 property
TransactionRulesResponseBody
object
2 properties
TransactionRuleCreateRequestBody
object
1 property
TransactionRuleCreateRequest
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-transaction-rules-api-openapi.yml Raw ↑

Other APIs MX Technologies publishes across the network.

MX Atrium API
MX SSO API
MX Data Access API
MX Batch API
MX Reporting API
MX Technologies accounts API
MX Technologies ach return API
MX Technologies budgets API
MX Technologies categories API
MX Technologies goals API
MX Technologies insights API
MX Technologies institutions API
Where this information came from

This is an independent, third-party profile of MX Technologies transaction rules 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.