fixed value “S256”

Value corresponding to the method used in the proof key (code_verifier) to derive the challenge (code_challenge).

psc

[optional]

lifetime

[optional]

login_hint

[optional]

redirect_uri

[optional]

state

[optional]

scope

[optional]

var crypto = require('crypto')
function base64URLEncode(str) {
    return str.toString('base64')
        .replace(/\+/g, '-')
        .replace(/\//g, ' _')
        .replace(/=/g, '');
}
 var verifier = base64URLEncode(crypto.randomBytes(32));
console.log("verifier: " + verifier);
function sha256(buffer) {
    return crypto.createHash('sha256').update(buffer).digest();
}</span >
var challenge = base64URLEncode(sha256(verifier));
console.log("challenge: " + challenge);

249 (TOKEN_VALIDITY_INVALID)

250 (INVALID_ACCESS_TOKEN)

209 (BAD_AUTHENTICATION)

401 (UNAUTHORIZED)</ td>

205

(REQUEST_BAD_DATA)

Returned when:< /p>

– There is no certificate in the PSC slot;

– The Alias provided does not match any certificate in the PSC slot.

224

(ERROR_DURING_AUTHENTICATION)

Redo the request after reviewing it, ensuring that it is in accordance with the method’s expectations.</span >

If the error persists, contact Certillion support.

{{token: }}

Receives the value of the access_token that could have been generated by either the 1.1 client_token call or the 2.2 token call.

application/json

The content of the request body must be in JSON format.

{
“client_id”: “{CLIENT_ID}”

“name”: “{NAME}” 

“{REDIRECT_URIS}
],
“email”: “{EMAIL}”
}

Redo the request after reviewing it and ensuring that its format is as expected by the method.

If the error persists, contact Certillion support.

application/x-www-form-urlencoded

The body of the request when sent has the format of a query string separated by &.

{  
  “client_id”: "{CLIENT_ID}",
  “client_secret”: "{CLIENT_SECRET}",
  “grant_type”: "{GRANT_TYPE}",
  “lifetime”: "{LIFETIME}"
}

Returned when:

– There is no transaction associated with the passed transaction id;

– The transaction ndoes not belong to the company that made the request;

Returned when:

– There is no valid signature to perform the download;

– The signature pattern used in the transaction does not accept the download;

Redo the request after reviewing it to ensure that it complies with the method’s expectations.

If the error persists, contact Certillion support.

Redo the request after reviewing it, ensuring that it complies with the method’s expectations.

If the error persists, contact Certillion support.

multipart/form-data

Allows the sending of large amounts of binary data, useful for sending large batches of files

{

“file”: “{FILE}”

}

method.

If the error persists, contact Certillion support.

{
  “client_id”: "{CLIENT_ID}",
  “client_secret": "{CLIENT_SECRET}",
  “user_cpf_cnpj": "{CPF}",
  “val_cpf_cnpj": "{USERNAME}"
}

Returned when:

– The credentials passed are incorrect;

– There is no OTP for the user;

– The OTP passed is invalid.

Redo the request after reviewing it ensuring that it is in accordance with what is expected by the method.

If the error persists, contact support. Certillion.

application/json

The body content of the request must be in JSON format.

{
  “client_id”: "{CLIENT_ID},

  “otp”: "{OTP}",

  “scope”: "{SCOPE}",

  “lifetime”: "{LIFETIME}"
}

psc_id

[optional]

psc_secret

[optional]

psc</ span>

[optional]

Returned when:

– The PSC you want to use is disabled;</ span>

– The signature pattern used in the transaction does not accept the download;

Redo the request after reviewing it, ensuring that it is in accordance with the method’s expectations.</span >

If the error persists, contact Certillion support.

application/json

The content of the request body must be in JSON format.

{
  “client_id”: "{CLIENT_ID}", 
  “client_secret”: "{CLIENT_SECRET}",
  “username”: "{USERNAME}",
  “password”: "{PASSWORD}",
  “scope”: "{SCOPE} ",
  "lifetime":"{LIFETIME}",
  "psc": "{PSC}"
}

certificate_alias

[optional]

Position on the x-axis from the left margin.

Default: 0

Position on the y-axis from the bottom margin.

Default: 0

Signature field height.

Default: 100

Position of the signature image on the PDF document page. Possible values: LEFT, RIGHT, TOP, BOTTOM, BACKGROUND

Default: LEFT

Increases or decreases the size of the signature image.

Default 1.0

The page on which the visual signature will be inserted.

Default: 1

Signature position on the page.

Possible values: TOP_LEFT, TOP_CENTER

< span style=”font-weight: 400;”>TOP_RIGHT, CENTER_LEFT, MIDDLE, CENTER_RIGHT, BOTTOM_LEFT, BOTTOM_CENTER, BOTTOM_RIGHT.

Default: TOP_LEFT

Alignment of the signature text.

Possible values: LEFT, RIGHT, CENTER.

Default: LEFT

Font that will be used in the signature text.

Possible values: HELVETICA, TIMES_ROMAN, COURIER.

Default: HELVETICA

Font size used in the text signature.

Default: 10

Signature text padding.

Default: 0

Signature rotation angle. Possible values: NONE, ROTATION_90 , ROTATION_180 , ROTATION_270

Default: NONE

Signature field width.

Default: 200

249 (TOKEN_VALIDITY_INVALID)

250 (INVALID_ACCESS_TOKEN)

209 (BAD_AUTHENTICATION)

807 (INVALID_CREDENTIALS)

Returned when the type of document sent does not match the requested signature standard

e.g.: XML document sent for a PAdES signature that requires PDF.

Remake the request using a valid certificate for the requested policy.

obs: ICP-Br policies only accept ICP-Br certificates

224

(ERROR_DURING_AUTHENTICATION)

Redo the request after reviewing it to ensure that it is as expected by the method.

If the error persists, contact Certillion support.

{{token}}

Receives the value of the access_token that may have been generated by either call 1.1 client_token or call 2.2 token.

application/json

The content of the request body must be in JSON format. 

“signature_policy”: “SIGNATURE_POLICY”,
“pki_name”: “{PKI_NAME}”,
“detached”: {DETACHED},
“hashes”: [
{
“id”: “{ID}”,

“alias”: “{ALIAS}”,

“hash”: “{DOCUMENTO_HASH}”

}
]
}

Returned when:

– The informed PSC is not valid;

– The informed PSC is disabled.

Remake the request by correctly filling in the code or manager_secret parameter.

If you do not have a callback URL registered, contact Certillion support.

Returned when:

– The code parameter is wrong;

– The manager_id parameter is invalid;

– The company does not have a previously registered callback URL;

Remake the request by correctly filling in the code or manager_secret parameter.

If you do not have a registered callback URL, contact Certillion support.

Returned when:

– The manager_id, code or code_verifier parameter is empty;

– The PSC does not have a valid certificate to use in a signature;

Remake the request filling in the missing parameter.

If the PSC does not have a valid certificate, it will be necessary to contact the PSC to obtain a new certificate.

Redo the request after reviewing it to ensure that it complies with the method’s expectations.

If the error persists, contact Certillion support.

{
  “client_secret”: "{CLIENT_SECRET}",
  “client_id": "{CLIENT_ID}",
  “code”: "{CODE}",
  “ code_verifier": "{CODE_VERIFIER}",
  “grant_type”: "{GRANT_TYPE}",</span >
  “manager_id”: "{MANAGER_ID}",
   “manager_secret”: "{MANAGER_SECRET}",
"psc": "{PSC}"
}

var crypto = require('crypto')
function base64URLEncode(str) {
   return str.toString('base64')
        .replace(/\+/g, '-')< br class="xliff-newline" />        .replace(/\//g, '_')
        .replace(/=/g, '');
}
var verifier = base64URLEncode(crypto.randomBytes(32));
console.log("verifier: " + verifier); 
function sha256(buffer) {
   return crypto.createHash('sha256').update(buffer).digest();
}
var challenge = base64URLEncode(sha256(verifier));
console.log("challenge: " + challenge);

250 (INVALID_ACCESS_TOKEN)

209 (BAD_AUTHENTICATION)

205

(REQUEST_BAD_DATA)

224

(ERROR_DURING_AUTHENTICATION)

Remake the request after reviewing it, ensuring that it complies with the method’s expectations.

If the error persists, contact Certillion support.

{{token}}

Receives the value of the access_token that may have been generated by either the 1.1 client_token call as for the 2.2 token call.

application/json

The content of the request body must be in JSON format.

</ td>

Redo the request after reviewing it ensuring thatits format is as expected by the method.

If the error persists, contact Certillion support.

application/json

The content of the request body must be in JSON format.

{
  “client_id”: "{CLIENT_ID}",
  “client_secret": "{CLIENT_SECRET}",
  “user_cpf_cnpj": "{CPF}",
  “val_cpf_cnpj": "{USERNAME}",
  “psc": class="xliff-newline" />}

250 (INVALID_ACCESS_TOKEN)

209 (BAD_AUTHENTICATION)

205

(REQUEST_BAD_DATA)

Returned when:</p >

– The certificate chain is incomplete;

– The certificate chain is invalid;

– There is a cryptographic error in the signature;

– There is an error in the signature encoding;

– The algorithm used to perform the signature is not supported by Certillion;

– The file format is not supported;

– Signature verification failed;

– Signature policy verification failed;

205

(REQUEST_BAD_DATA)</ p>

Redo the request after reviewing it, ensuring that it is in accordance with the method’s expectations.

If the error persists, contact Certillion support.

{{token}}

Receives the value of the access_token that may have been generated by either the 1.1 client_token call or the 2.2 token call.

application/json

The content of the request body must be in JSON format.

{
  “signature”: “{SIGNATURE}”,
  “content”: "{CONTENT}",
  “document_hash”: "{DOCUMENTO_HASH}",
  “pki_name ": "{PKI_NAME}"
}

610< /td>

722< /td>