Skip to main content
GET
Fee configuration

Authorizations

x-api-key
string
header
required

Soft-auth read routes accept x-api-key with a publishable or partner key; money-moving routes require a secret partner key in Authorization: Bearer.

Headers

x-api-key
string
required

Response

200 - application/json
integrator
string
required

Integrator identity the fee is resolved for — your partner slug, or the public default.

Example:

"hypermid"

fee
number
required

Fee as a fraction (feeBps/10000).

Example:

0.003

feeBps
number
required

Fee in basis points (100 bps = 1%). The same value as fee, expressed as an integer.

Example:

30

partner
string

Partner name when resolved via X-API-Key.