curl --request POST \
  --url https://api.bmpdigital.moneyp.dev.br/Proposta/IncluirCampoExtra \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --header 'IdempotencyKey: <idempotencykey>' \
  --data '{
  "dto": {
    "codigoProposta": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "codigoOperacao": "<string>",
    "numeroProposta": 123
  },
  "camposExtras": [
    {
      "nomeCampo": "<string>",
      "valorCampo": "<string>"
    }
  ]
}'
{
  "msg": "<string>",
  "hasError": true,
  "messages": [
    {
      "messageType": 1,
      "code": "<string>",
      "context": "<string>",
      "description": "<string>",
      "field": "<string>"
    }
  ],
  "parametros": [
    {
      "nome": "<string>",
      "valor": "<string>"
    }
  ]
}

Through this endpoint, the partner inserts unlimited extra fields for use in the printing of CCB. These fields should not be used by our analysts for interpreting business rules. With each submission, previous values are deleted. The process for utilization is: • Define field names in conjunction with our integration technical team. • Define the usage location for each of the extra fields. • Submit the proposal through one of the available methods. • Send the extra fields; the method allows for receiving a list containing “FieldName” and “FieldValue”. • When updating one of the extra fields, the entire batch of fields must be resent. • FieldName is limited to 30 alphanumeric characters. • FieldValue has an unlimited size.

Authorizations

​
Authorization
string
header
required

Informe o token

Headers

​
IdempotencyKey
string
required

Body

​
dto
object
​
camposExtras
object[] | null

Response

200
text/plain
OK
​
msg
string | null
​
hasError
boolean
​
messages
object[] | null
​
parametros
object[] | null

Was this page helpful?