curl --request POST \
  --url https://api.bmpdigital.moneyp.dev.br/Proposta/IncluirAssinaturaCCB \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --header 'IdempotencyKey: <idempotencykey>' \
  --data '{
  "dto": {
    "codigoProposta": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "codigoOperacao": "<string>",
    "numeroProposta": 123
  },
  "assinantes": [
    {
      "nome": "<string>",
      "email": "<string>",
      "documento": "<string>",
      "descricao": "<string>",
      "telefoneCelular": "<string>",
      "notificarPorEmail": true,
      "notificarPorWhatsApp": true,
      "notificarPorSMS": true,
      "codigoIdentificador": "<string>",
      "dtLimiteAssinatura": "2023-11-07T05:31:56Z"
    }
  ]
}'
{
  "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 will be directed to our environment to sign the proposal.

  • In this context, the inclusion of proposal signatories is permitted.
  • The standard procedure determines that the proposal can only be finalized if all registered signatories have signed the proposal. Therefore, according to the prominent ones, the auxiliary system will control the signatures of each individual.
  • The signatories who receive the notification by email will have access to the proposal to sign it and will also be able to manage pending signatures, as long as they are parameterized for this, and can notify the signatories.
  • The method requires the authentication and location parameters of the proposal, as well as a list of signatories.

​
Messaging

Authorizations

​
Authorization
string
header
required

Informe o token

Headers

​
IdempotencyKey
string
required

Body

Response

200
text/plain

OK

The response is of type object.