Update customer settings data

PUT {{baseUrl}}/Global/v1/customer/settings

Update ERP customer settings data.

Schema Definitions

Request

Attribute	Data type	Description
pfxFile	String	Certificate file. Use a file converted to a base64 string.
pfxPassword	String	Password string for the certificate.
logoFile	String	Jpg file for the customer. Use a file converted to a base64 string.
nfSeEnvironment	String	NFSe environment. Use homolog or prod.
nfSeExtraParameters	String	Extra parameters for the NFSe component.
city	String	Customer city.
companyTaxCode	String	The CNPJ number for the lot number. Could be the provider CNPJ or the company's own CNPJ.
companyStateTaxCode	String	Company's State tax code (inscrição estadual).
companyCityTaxCode	String	City Tax Code for the company (inscrição municipal).
state	String	Customer state.

Response

Attribute	Data type	Description
success	Boolean	Boolean indicating if the operation was sucessfull.
message	String	Operation custom message.
data	String	Empty / null.

Request Body

{"pfxFile"=>"<string>", "pfxPassword"=>"<string>", "logoFile"=>"<string>", "nfSeEnvironment"=>"<string>", "nfSeExtraParameters"=>"<string>", "city"=>"<string>", "companyTaxCode"=>"<string>", "companyStateTaxCode"=>"<string>", "companyCityTaxCode"=>"<string>", "state"=>"<string>"}

HEADERS

Key	Datatype	Description
`CustomerApplicationID`	null	(Required) Customer Application ID provided by the API's owner
`ResponseDemo`	null	Enter "ReturnTypeD", "ReturnTypeI", "ProcessStatus2" or "ProcessStatus3" for demo values
`Content-Type`	string	The Content-Type header field is used to specify the nature of the data in the body of an entity. OAS REST APIs support application/json.
`Accept`	string	The Accept request HTTP header indicates which content types, expressed as MIME types, the client is able to understand. OAS REST APIs support text/plain.

RESPONSES

status: OK

{&quot;success&quot;:true,&quot;message&quot;:&quot;Customer settings updated.&quot;,&quot;data&quot;:&quot;&quot;}