Update or replace a contract by including the id of the contract as a path parameter.
name, is_active, is_default, is_per_carrier_default).
However, used contracts are immutable, if you change the contract_data of a contract that has already been used for shipments,
it will cause a new contract ID to be created. In this case, the old one will no longer be active for use.
After updating a contract with contract_data, we need to validate it again and its state will be "validating".
During the validation the contract is not active and cannot be used for creating shipments. The validation
process is asynchronous and will happen in the background.
Once validation is complete, the contract’s state will change to one of the following:
"active" or "inactive": The contract has been successfully processed."validation_failed": An error occurred during validation. Additional information about the failure will be provided.Basic Authentication using API key and secrets is currently the main authentication mechanism.
The id of the contract.
Update request object model
New contracts are inactive by default, if you want to activate it immediately set this flag.
false
Marks the contract as default for a carrier. You can have only one default direct contract per carrier.
Note: You cannot mark a contract as not default, to switch the default contract of a carrier use is_default_per_carrier: true on the contract you like to set as active, other contracts for this carrier will automatically be marked as not default.
false
Fields for creating a contract. It supports dynamic key-value pairs, where keys represent field names and values are string-based data.
{
"country": "NL",
"client_id": "sendcloud-1"
}The name of the contract
50"main"
OK
Update contract
User contract