Reads the calling operator's own effective collection configuration.
POST
/api/resellers/get-own-effective-collection-configuration-async
deprecated
Requires: Resellers.Resellers.Update, reseller scope.
The effective configuration is the one that governs the reseller's merchant billing after inheritance from its ancestors has been applied. The reseller is resolved from the signed-in user, so this route takes no reseller id and cannot be pointed at another reseller. A caller with no reseller of its own, an administrator for instance, is refused; use the id-taking read instead.
Signed in, you can send this request to your own sandbox merchant from the console and read the answer. Sign in to try it.
Example request
Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.
The request body is a . See the Request body section below for its fields.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
suppressNulls
required |
query | boolean | If true, omit properties with null values. |
Request body
application/json
, required
| Field | Type | Description |
|---|
This request body has no documented fields.
Responses
200 OK
Body: EffectiveCollectionConfigurationDto
Each item has these fields.
| Field | Type | Description |
|---|---|---|
resellerId
required |
string (uuid) | The reseller the configuration was resolved for. |
sourceResellerId
required |
string (uuid) | The reseller whose configuration applies. Equal to `resellerId` when the reseller is governed by its own configuration, or when nothing is configured on it or any ancestor. |
sourceResellerName
required |
string | The display name of `sourceResellerId`, when it resolved. nullable |
isInherited
required |
boolean | Whether the configuration comes from an ancestor rather than the reseller itself. |
isConfigured
required |
boolean | Whether a collection merchant is configured on the effective set. |
defaultFulfillmentPath
required |
all of BillingFulfillmentPath | The effective default fulfillment path. nullable |
collectionMerchantId
required |
string (uuid) | The effective collection merchant. nullable |
captureHppPageId
required |
string (uuid) | The effective card-capture Hosted Payment Page. nullable |
allowCardPayments
required |
boolean | The effective card allow flag. An unset flag permits card capture. nullable |
allowAchPayments
required |
boolean | The effective ACH allow flag. An unset flag permits ACH capture. nullable |
This response has no documented body fields.
403 Forbidden
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
401 Unauthorized
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
400 Bad Request
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
404 Not Found
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
501 Not Implemented
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
500 Internal Server Error
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
default The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
429 The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
Errors
A failed request returns the platform error envelope. The
error reference lists every value
error.code can carry and shows the four response shapes.