central-bank-transaction-limits
Operations addressed under /central-bank-transaction-limits — 3 operations.
create-central-bank-transaction-limit
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route returns AuraCommandDto<Guid>, which is the response body itself and not a wrapper around one: the framework declares it as a class with a single property, Id, of type Guid. A caller gets a JSON OBJECT with one field, not a bare value. The field is id on the wire.
| Field | Name on the wire | Declared type | Nullable |
|---|---|---|---|
Id | id | Guid | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_MNYTRNS_62 | 400 | LIMIT_ALSO_FOUND_FOUND | The definition you want to add is available |
create-central-bank-transaction-limit › Request Body
descriptionlimitTypePermitted values — validated against the limit_type parameter.
| Value | Meaning |
|---|---|
1 | Havale |
2 | Virman |
3 | Eft |
4 | Fast |
5 | Kart |
6 | QR |
Permitted values — validated against the limit_type parameter. The service rejects any other value.
| Value | Token | Labels |
|---|---|---|
1 | Havale | no label seeded |
2 | Virman | no label seeded |
3 | Eft | no label seeded |
4 | Fast | no label seeded |
5 | Kart | no label seeded |
6 | QR | no label seeded |
maxAmountLimitminAmountLimitcreate-central-bank-transaction-limit › Responses
Success. An exact, uniquely bound route registration declares the command-id envelope, so this schema is the code-backed body contract.
idIdentifier returned by the command.
update-central-bank-transaction-limit
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_MNYTRNS_62 | 400 | LIMIT_ALSO_FOUND_FOUND | The definition you want to add is available |
ERR_MNYTRNS_63 | 400 | LIMIT_NOT_FOUND | Transaction limit is not found. |
path Parameters
idupdate-central-bank-transaction-limit › Request Body
descriptionlimitTypePermitted values — validated against the limit_type parameter.
| Value | Meaning |
|---|---|
1 | Havale |
2 | Virman |
3 | Eft |
4 | Fast |
5 | Kart |
6 | QR |
Permitted values — validated against the limit_type parameter. The service rejects any other value.
| Value | Token | Labels |
|---|---|---|
1 | Havale | no label seeded |
2 | Virman | no label seeded |
3 | Eft | no label seeded |
4 | Fast | no label seeded |
5 | Kart | no label seeded |
6 | QR | no label seeded |
maxAmountLimitminAmountLimitupdate-central-bank-transaction-limit › Responses
Success. The catalog declares no response fields for this operation. The body is UNKNOWN CONTENT. The response type this route registers was read from the service's own source and is published on this operation as x-aura-code-response.
delete-central-bank-transaction-limit
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_MNYTRNS_63 | 400 | LIMIT_NOT_FOUND | Transaction limit is not found. |
path Parameters
iddelete-central-bank-transaction-limit › Responses
Success. The catalog declares no response fields for this operation. The body is UNKNOWN CONTENT. The response type this route registers was read from the service's own source and is published on this operation as x-aura-code-response.