curl --request POST \
  --url https://api.bmpdigital.moneyp.dev.br/Proposta/IncluirAssinaturaCCBFinalizada \
  --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,
      "dtAssinatura": "2023-11-07T05:31:56Z",
      "ipAssinatura": "<string>"
    }
  ]
}'
{
  "msg": "<string>",
  "hasError": true,
  "messages": [
    {
      "messageType": 1,
      "code": "<string>",
      "context": "<string>",
      "description": "<string>",
      "field": "<string>"
    }
  ],
  "parametros": [
    {
      "nome": "<string>",
      "valor": "<string>"
    }
  ]
}
Using the proposal completion endpoint is mandatory
  • Through this endpoint, the partner can sign the proposal. It allows the inclusion of signatories who have already signed in the integrator’s backend, as the proposal is only finalized after all registered signatories have signed.
  • This method does not send email notifications requesting signatures.
  • The method requires authentication and proposal location parameters, as well as a list of signatories who have already signed, including the date, time, and originating IP address.

Authorizations

Authorization
string
header
required

Informe o token

Headers

IdempotencyKey
string
required

Body

dto
object
assinantes
object[] | null

Response

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