Update
POST/updateConnector/:connectorGuid
Create connector with the given identifier.
Request
Path Parameters
Identifier of the connector.
- application/json
Bodyrequired
required
The connector to update.
Array [
]
Possible values: >= 3 characters
SimulatorConnector AAdapter identifier.
SimulatorMethod identifier.
Credit CardConnector API key.
sim-connector-aConnector public integration key, user for payment.js.
4nhDxztY3bBeozkyd7ZsConnector shared secret.
If left empty the sharedSecret will be generated automatically.
Possible values: <= 50 characters
OsEPpNrSr8hxYR3BO0F73YXMvMdDsMISO 3166-1 alpha-2 country code.
Possible values: Value must match regular expression ^[A-Z]{2}$
ATconfig
object
Connector configuration.
asmithsupersecure1ljkllLkklmKLlk3extraData
object
Configuration values.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter.
Configuration values.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter.
nullISO 639-1 language code.
Possible values: Value must match regular expression ^[a-z]{2}$
deWhether the connector is in test mode.
truevault
object
Configuration values for vault connectors.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId/:merchantGuid endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter and merchant in use.
Configuration values for vault connectors.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId/:merchantGuid endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter and merchant in use.
Connector configuration.
Customer profile Container ID.
falseList of transaction type disabled for this connector.
Possible values: [initial_debit, initial_preauthorize, capture, partial_capture, refund, partial_refund, register, deregister, payout, recurring_debit, recurring_preauthorize]
Possible values: [inherit, json, xml]
inheritProvider identifier.
Whether the scheduler is enabled.
Whether the virtual terminal is enabled.
Identifier of risk rule profile for virtual terminal.
settings
object
Set connector alias for global routing.
terminals
object[]
Unique terminal identifier.
Set current STAN.
Set current capture reference.
routingMetaConnector
object
On create/update add this to create a classic routing meta-connector (adapter and method must be set to MetaConnector).
Identifier of the default connector to route to.
Whether to re-route recurring transactions to the original connector.
falsemultiMethodMetaConnector
object
On create/update add this to create a multi-method meta-connector (adapter and method must be set to MetaConnector).
If no action is configured (rules), the default action is to disable the connector.
How many retries should be allowed if possible.
Possible values: <= 9
Expiry time in hours.
addSettings
object
removeSettings
object
Responses
- 200
- 401
- 422
- 500
The created merchant user.
- application/json
- Schema
- Example (from schema)
- Example
Schema
Array [
]
Whether the request was successful or not.
connector
object
Identifier.
CO-1234-1234-1234-1234-1234-1234Possible values: >= 3 characters
SimulatorConnector AAdapter identifier.
SimulatorMethod identifier.
Credit CardConnector API key.
sim-connector-aConnector public integration key, user for payment.js.
4nhDxztY3bBeozkyd7ZsConnector shared secret.
If left empty the sharedSecret will be generated automatically.
Possible values: <= 50 characters
OsEPpNrSr8hxYR3BO0F73YXMvMdDsMISO 3166-1 alpha-2 country code.
Possible values: Value must match regular expression ^[A-Z]{2}$
ATconfig
object
Connector configuration.
asmithsupersecure1ljkllLkklmKLlk3extraData
object
Configuration values.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter.
Configuration values.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter.
nullISO 639-1 language code.
Possible values: Value must match regular expression ^[a-z]{2}$
deWhether the connector is in test mode.
truevault
object
Configuration values for vault connectors.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId/:merchantGuid endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter and merchant in use.
Configuration values for vault connectors.
To obtain valid configuration values, use the /api/provisioning/getConnectorSettings/:adapterId/:merchantGuid endpoint.
This endpoint provides the necessary configuration values tailored to the specific adapter and merchant in use.
Connector configuration.
2001-02-03T04:05:06+02:00Customer profile Container ID.
falseList of transaction type disabled for this connector.
Possible values: [initial_debit, initial_preauthorize, capture, partial_capture, refund, partial_refund, register, deregister, payout, recurring_debit, recurring_preauthorize]
Merchant identifier.
ME-1234-1234-1234-1234-1234-1234Whether the connector is a meta-connector.
falsePossible values: [inherit, json, xml]
inheritProvider identifier.
Whether the scheduler is enabled.
Whether the virtual terminal is enabled.
Identifier of risk rule profile for virtual terminal.
settings
object
Set connector alias for global routing.
terminals
object[]
Unique terminal identifier.
routingMetaConnector
object
On create/update add this to create a classic routing meta-connector (adapter and method must be set to MetaConnector).
Identifier of the default connector to route to.
Whether to re-route recurring transactions to the original connector.
falsemultiMethodMetaConnector
object
On create/update add this to create a multi-method meta-connector (adapter and method must be set to MetaConnector).
If no action is configured (rules), the default action is to disable the connector.
How many retries should be allowed if possible.
Possible values: <= 9
Expiry time in hours.
{
"success": true,
"connector": {
"guid": "CO-1234-1234-1234-1234-1234-1234",
"name": "SimulatorConnector A",
"adapter": "Simulator",
"method": "Credit Card",
"apiKey": "sim-connector-a",
"publicIntegrationKey": "4nhDxztY3bBeozkyd7Zs",
"sharedSecret": "OsEPpNrSr8hxYR3BO0F73YXMvMdDsM",
"archived": true,
"businessCountry": "AT",
"config": {
"username": "asmith",
"password": "supersecure1",
"apiSecret": "ljkllLkklmKLlk3",
"extraData": null,
"language": "de",
"testMode": true,
"vault": {}
},
"createdAt": "2001-02-03T04:05:06+02:00",
"customerProfileContainer": 0,
"defaultRiskRuleSet": 0,
"description": "string",
"disabled": false,
"disabledTransactionTypes": [
"initial_debit"
],
"merchantGuid": "ME-1234-1234-1234-1234-1234-1234",
"isMetaConnector": false,
"postbackFormat": "inherit",
"provider": "string",
"scheduleApiAvailable": true,
"virtualTerminalAvailable": true,
"vtRiskRuleSet": 0,
"settings": {
"tx:expiration-minutes": "900",
"refund:ui-enabled": "1"
},
"alias": "string",
"terminals": [
{
"terminalId": "string",
"disabled": true
}
],
"routingMetaConnector": {
"defaultConnector": "string",
"reRouteRecurring": false
},
"multiMethodMetaConnector": {
"defaultActionDisableConnector": true,
"retries": 0,
"expiry": 0
}
}
}
{
"success": true,
"connector": {
"guid": "CO-4321-4321-4321-4321-4321-4321",
"name": "SimulatorConnector C",
"Adapter": "Simulator",
"method": "Creditcard",
"APIKey": "sim-connector-c",
"publicIntegrationKey": "XTcSyLgJ04b7cHkvKScG",
"sharedSecret": "V0WkgQPsHAUH4iXCsqWGYDeFKc4O6G",
"archived": false,
"businessCountry": "DE",
"config": {
"username": "new-uname",
"password": "new-pw",
"APISecret": "new-sikret",
"extraData": {
"setting": "test"
},
"language": "de",
"testMode": false
},
"createdAt": "2020-12-16T09:57:14+00:00",
"customerProfileContainer": null,
"defaultRiskRuleSet": 213,
"description": "My test Connector",
"disabled": false,
"disabledTransactionTypes": [
"refund"
],
"MerchantGUID": "ME-1234-1234-1234-1234-1234-1234",
"isMetaConnector": false,
"postbackFormat": "inherit",
"provider": "PR-1234-1234-1234-1234-1234",
"alias": "default",
"scheduleAPIAvailable": true,
"virtualTerminalAvailable": true,
"vtRiskRuleSet": null,
"terminals": [
{
"terminalId": "ID-0001",
"disabled": false
}
],
"settings": {
"tx:expiration-minutes": 100
}
}
}
Unauthorized, see authentication.
- application/json
- Schema
- Example (from schema)
- 1000
Schema
1000- Unauthorized, e.g. invalid credentials1001- The request is invalid1002- The value does not comply to the requirements, e.g. pre-defined values1003- The format is invalid1004- The value contains invalid characters1005- Mandatory parameters are missing1006- Some parameters are not applicable in given request scenario1007- The provided entity does not exist9999- Internal system error
true if successful.
Error code.
1004Human readable error message.
:::info
While the errorMessage field provides useful context for understanding the nature of the error, it's important to note that the content of this message can vary based on specific circumstances.
For consistent and reliable error handling in your application, always base your logic on the errorCode field, not the errorMessage.
:::
name: nameInvalid characters{
"success": true,
"errorCode": 1004,
"errorMessage": "name: nameInvalid characters"
}
Unauthorized (1000)
{
"success": false,
"errorCode": 1000,
"errorMessage": "Unauthorized"
}
Unprocessable entity.
- application/json
- Schema
- Example (from schema)
- 1001
Schema
1000- Unauthorized, e.g. invalid credentials1001- The request is invalid1002- The value does not comply to the requirements, e.g. pre-defined values1003- The format is invalid1004- The value contains invalid characters1005- Mandatory parameters are missing1006- Some parameters are not applicable in given request scenario1007- The provided entity does not exist9999- Internal system error
true if successful.
Error code.
1004Human readable error message.
:::info
While the errorMessage field provides useful context for understanding the nature of the error, it's important to note that the content of this message can vary based on specific circumstances.
For consistent and reliable error handling in your application, always base your logic on the errorCode field, not the errorMessage.
:::
name: nameInvalid characters{
"success": true,
"errorCode": 1004,
"errorMessage": "name: nameInvalid characters"
}
Unprocessable entity (1001)
{
"success": false,
"errorCode": 1001,
"errorMessage": "Unauthorized"
}
Internal server error.
- application/json
- Schema
- Example (from schema)
- 1001
Schema
1000- Unauthorized, e.g. invalid credentials1001- The request is invalid1002- The value does not comply to the requirements, e.g. pre-defined values1003- The format is invalid1004- The value contains invalid characters1005- Mandatory parameters are missing1006- Some parameters are not applicable in given request scenario1007- The provided entity does not exist9999- Internal system error
true if successful.
Error code.
1004Human readable error message.
:::info
While the errorMessage field provides useful context for understanding the nature of the error, it's important to note that the content of this message can vary based on specific circumstances.
For consistent and reliable error handling in your application, always base your logic on the errorCode field, not the errorMessage.
:::
name: nameInvalid characters{
"success": true,
"errorCode": 1004,
"errorMessage": "name: nameInvalid characters"
}
Internal server error (9999)
{
"success": false,
"errorCode": 9999,
"errorMessage": "Internal server error"
}