Check signature

Answers whether a person already accepted one of the two documents, so you do not have to keep anything from the call that issued their link.

GET/v1/tyc/signatures/{dni}

Request

Headers

Field	Type	Required	Description
Authorization	string	Yes	Access token in Bearer ACCESS_TOKEN format

Path Parameters

Field	Type	Required	Description
dni	string	Yes	7 or 8 digits. Digits only — no dots.

Query Parameters

kind has no default

The document is named rather than guessed — the same as when you ask for the link.

• The two are different documents: a signed VINCULATION link is consent to the linkage rather than to the terms.
• Answering about the wrong one would be worse than refusing to answer.

Field	Type	Required	Description
kind	string	Yes	TYC or VINCULATION. Which document you are asking about. Case-sensitive.

Not applicable: Body.

Response

2XX Success

Status: 200 OK

Somebody who has not signed answers the same shape, so nothing appears or disappears between the two cases:

{
  "dni": "37087294",
  "kind": "TYC",
  "signed": false,
  "document_version": null,
  "signed_at": null
}

Field	Type	Description
dni	string	The document you asked about.
kind	string	The document you asked about, echoed back.
signed	boolean	Whether that person accepted that document.
document_version	string | null	What they accepted, exactly as it was sent to the accept call. null when signed is false.
signed_at	string | null	When they accepted. ISO 8601, UTC. null when signed is false.

A person you never asked for a link for answers exactly like one who has links but has not signed: signed is false. The two are different in our records but not in what you do next.

If the same person signs the same document twice — possible, since asking for a new link only retires the one they had not used — the answer is the later signature.

The answer covers the links you asked for. It is not a lookup of every signature that person may have given Allaria through another channel.

Error Codes

Status	Description
401	Unauthorized — invalid or missing access token
403	Forbidden — your client_id is not authorized for this endpoint
422	Unprocessable Entity — dni is not 7 or 8 digits, or kind is missing or not one of the two values
500	Internal Server Error — {"error": "internal_error"}

Error structure (422):

{
  "error": "invalid_payload",
  "detail": "kind Field required",
  "problems": [
    { "field": "kind", "message": "Field required" }
  ]
}

Code Example

cURL

curl -X GET "https://b2b.allaria.cloud/v1/tyc/signatures/37087294?kind=TYC" \
  -H "Authorization: Bearer ACCESS_TOKEN"

JavaScript

const response = await fetch('https://b2b.allaria.cloud/v1/tyc/signatures/37087294?kind=TYC', {
  method: 'GET',
  headers: { 'Authorization': 'Bearer ACCESS_TOKEN' }
});
const data = await response.json();
console.log(data.signed);

Python

import requests
response = requests.get(
  'https://b2b.allaria.cloud/v1/tyc/signatures/37087294',
  params={ 'kind': 'TYC' },
  headers={ 'Authorization': 'Bearer ACCESS_TOKEN' }
)
data = response.json()
print(data['signed'])

Node.js

const axios = require('axios');
const response = await axios.get('https://b2b.allaria.cloud/v1/tyc/signatures/37087294', {
  params: { kind: 'TYC' },
  headers: { Authorization: 'Bearer ACCESS_TOKEN' }
});
console.log(response.data.signed);

2XX Success

{
  "dni": "37087294",
  "kind": "TYC",
  "signed": true,
  "document_version": "tyc-v3-2026-08",
  "signed_at": "2026-09-22T19:14:19Z"
}