Returns the configuration field schema for one processor.
GET
/api/processors/{processorId}/config-schema
deprecated
Requires: Transactions.ProcessorConfiguration.ViewSchema, merchant scope.
Optionally scoped to the given payment types.
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 |
|---|---|---|---|
processorId
required |
path | string | The processor identifier (e.g. "tsys"). |
paymentTypes
required |
query | array of string | Optional payment type names to filter the schema to; omit for universally-applicable fields only. |
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: ProcessorConfigSchemaDto
Each item has these fields.
| Field | Type | Description |
|---|---|---|
processorId
required |
string | Identifier of the processor this schema describes. Submit this as the processor configuration's `ProcessorId` in a merchant create/update request. nullable |
processorName
required |
string | Display name of the processor. nullable |
fields
required |
array of ProcessorFieldDefinitionDto | The fields applicable to the requested payment types, ordered by `position`. nullable |
schemaVersion
required |
string | Opaque, deterministic content hash of this processor's full projected field schema. It is derived from the field definitions (not hand-maintained), so it changes whenever a field is added, removed, or edited, and is stable otherwise. It is <b>per-processor</b> (covers the whole field catalog), so it does not vary with the `paymentTypes` filter. Cache the schema keyed by this value to detect drift; it is also returned as the response `ETag`, and a request with a matching `If-None-Match` receives `304 Not Modified`. 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.