Enrol or replace the caller's signing PIN

POST

/api/v1/signing-credentials

const url = 'https://app.avera.io/api/v1/signing-credentials';
const options = {
  method: 'POST',
  headers: {'Content-Type': 'application/json'},
  body: '{"pin":"example"}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url https://app.avera.io/api/v1/signing-credentials \
  --header 'Content-Type: application/json' \
  --data '{ "pin": "example" }'

The signing PIN is bound to the user, not to a tenant: one enrolment covers every tenant the user participates in, with the PIN policy taken from the enrolling tenant. On first enrolment the internal CA issues the user’s X.509 signing certificate; re-enrolment reuses it. Historic signatures stay valid, because verification consults the credential that existed at signing time.

Request Body^required

application/json

object

pin

required

string

>= 1 characters

Example ^generated

{
  "pin": "example"
}

Responses

200

*/*

object

enrolled

required

boolean

certificateId

required

string

certificateSubjectDn

required

string

Enrol or replace the caller's signing PIN

Request Bodyrequired

Example generated

Responses

200

Request Body^required

Example ^generated