Correct Transaction Similarity Grouping

post

https://api-sandbox.thisisbud.com/corrections/v3/similar

Mark a given set of transaction IDs as similar to one-another, or to a given reference transaction ID. This improve's Bud's ability to detect regular transactions, and expands the set of transactions that are considered similar to one-another.

This endpoint can also be used to identify a set of transactions as not similar.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Expected request structure for the similarity correction endpoint

transaction_ids

array of strings

required

The transactions the rule applies to

transaction_ids*

similar

boolean

Defaults to false

Whether the specified transactions are similar to each other (or to reference_transaction_id, if supplied)

reference_transaction_id

string

The transaction whose group the specified transactions should join or leave. If omitted, the rule applies to the group formed by transaction_ids themselves.

Headers

X-Client-Id

string

required

The API Client Identifier (Service Application Identifier).

X-Customer-Id

uuid

required

A unique identifier for a Customer, as registered on Bud's platform.

X-Customer-Idempotent-Identifier

string

Use the internal client identifier, provided in the client_metadata object when creating the customer in Create Customer V3, in place of an X-Customer-Id header.

Responses

401

Unauthorised request

405

An unexpected HTTP method was used

5XX

An unexpected error occurred on the server side

Language

Credentials

OAuth2

Loading…

Response

Choose an example:

application/json

201The request was successfully processed

400The request contains an invalid payload.