E-Signature
Electronic signing of contracts.
POST/api/financing-cases/{financingCaseId}/start-esignature
Start the eSignature process for a financing case
Submits authorized persons and starts the eSignature process. The financing case must have a quote in FINANCE_ACCEPTED status. Where GRENKE has issued a statement on who may sign for this customer, the submitted persons must be covered by it: every person has to appear on the statement, and the submitted set has to be able to sign under the signing rule GRENKE gave. If it is not, the request is rejected with 422 and the reason is returned in the response body. Where GRENKE has issued no statement, the submitted persons are accepted as given; the only check is that they can validly sign at all, so a single person sent with `soloSigneePermitted: false` is rejected with 422.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| financingCaseId | path | string | yes | StartESignatureRequest identifier |
Request body
| Name | Type | Required | Description |
|---|---|---|---|
| authorizedPersons | array<AuthorizedPersonData> | yes | Persons authorized to sign; at least one is required. Generic mailbox addresses (for example info@) are rejected. A single person must be permitted to sign alone (soloSigneePermitted = true); otherwise provide at least two persons. |
Code samples
curl -X POST 'https://sandbox.partner.miete24.com/api/financing-cases/{financingCaseId}/start-esignature' \
-H 'X-Api-Key: YOUR_API_KEY'
const response = await fetch('https://sandbox.partner.miete24.com/api/financing-cases/{financingCaseId}/start-esignature', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
});
const data = await response.json();
Responses
| Status | Description | Schema |
|---|---|---|
| 200 | StartESignatureRequest resource created | StartESignatureRequest.StartESignatureResponse |
| 400 | Invalid input | — |
| 403 | Forbidden | — |
| 422 | Unprocessable entity | — |