Skip to main content
GET
Get partner configuration
Make this your first call in each environment. It verifies your app ID and app secret, then returns the app’s enabled modules, fee configuration, supported networks and assets, payment-method capability surface, webhook event catalog and Vault settings. The call is read-only and returns no secrets. It describes what the app can do, not what a particular Payment can use: payment methods depend on each Payment’s amount, destination, settlement and capability snapshot, so create the Payment and read its payment-methods endpoint for the exact list. See Authentication for the credential model and Capabilities for what each module unlocks.

Authorizations

Authorization
string
header
required

HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin.

Headers

Stableyard-Version
enum<string>

Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated.

Available options:
2026-09-09

Response

Partner configuration

id
string
required
Example:

"app_123"

appId
string
required
Example:

"app_123"

organizationId
string
required
Example:

"org_123"

environmentId
string
required
Example:

"env_123"

apiVersion
enum<string>
required

Immutable date-based contract recorded on the resource. Historical values may appear on existing records; only versions advertised in x-stableyard-supported-api-versions are accepted for new requests.

Available options:
2026-08-28,
2026-09-09
Example:

"2026-09-09"

supportedApiVersions
enum<string>[]
required

Immutable date-based contract recorded on the resource. Historical values may appear on existing records; only versions advertised in x-stableyard-supported-api-versions are accepted for new requests.

Available options:
2026-08-28,
2026-09-09
namespace
string
required
Example:

"partner"

scopes
string[]
required
Example:
credentialType
enum<string>
required

Standard keys dynamically receive permissions for enabled app products. Restricted keys retain an explicit scope subset.

Available options:
standard,
restricted
credentialMode
enum<string>
required

Identifies whether the request used a server app secret or a short-lived Partner Dashboard session.

Available options:
app_secret,
portal_session
status
string
required
Example:

"active"

modules
object[]
required
compliance
object
required
fees
object
required
networks
object[]
required
capabilities
object
required
integrations
object
required