Mobile-ID Sign · INTEGRATION & PRACTICE

Trusted SIC 1.7.260928 — Earlier-version documentation

1.7.260928 content is retained for comparison. Do not infer that these operations are described by Compact 1.7.261001 or active in production.

Developer Center Watch Agent demos

ON THIS PAGE

Coverage and integration prerequisites

Source documentation, contract confirmation, sandbox testing and production acceptance are separate stages. Website version changes do not advance readiness.

Review coverage for each operation

Per-operation readiness
Operation	Documentation	Contract	Sandbox
`POST /v2/credentials/authorize`	Selected fields	Deployment not confirmed	Not tested
`POST /v2/credentials/authorizeCheck`	Selected fields	Deployment not confirmed	Not tested
`POST /v2/signatures/signHash`	Selected fields	Deployment not confirmed	Not tested
`POST /v2/signatures/signPolling`	Selected fields	Deployment not confirmed	Not tested
`POST /v2/credentials/info`	Selected fields	Deployment not confirmed	Not tested

Download scope-specific OpenAPI · Download documentary Postman

Compare the newer version

SIC Compact and migration

Scope and assets

Source: Trusted SIC 1.7.260928. This OpenAPI subset contains 5 edited operations; the catalog retains the other source functions. This is not an accepted production contract.

OpenAPI JSON · 1.7.260928 OpenAPI YAML · 1.7.260928 Postman · 1.7.260928 Environment · 1.7.260928

Operations and data structures

POST/v2/credentials/authorize

Authorize document digests

Source documented · Deployment contract unconfirmed · Sandbox not tested

OperationId: SicAuthorize · Trusted SIC 1.7.260928 · PDF pages: 30, 31

Source-derived; deployment remains unconfirmed. Sample inputs are for reading, not live submission.

Preconditions and authentication

Select a credential and fix the digests and signature count. Bind the user interface to the correct requested content. Keep the Bearer token server-side; exclude tokens/SAD from frontend code and public logs.

Request · application/json

Request schema
Field	Type	Presence	Description
`credentialID`	string	Required	Credential identifier for the operation.
`numSignatures`	integer	Required	Number of signatures to authorize.
`documentDigests`	object	Required
`documentDigests.hashes`	string[]	Required	Base64 digests of the authorized content.
`documentDigests.hashAlgorithmOID`	string	Required	Hash algorithm OID; select using confirmed configuration.
`description`	string	Optional / source conditions	User-facing authorization description.
`agreementUUID`	string	Optional / source conditions	Client-data correlation identifier in the source.
`username`	string	Optional / source conditions	Username in the authorization context.
`clientInfo`	object	Optional / source conditions
`clientInfo.application`	string	Optional / source conditions	Originating application name.
`view`	object	Optional / source conditions
`view.lang`	string	Optional / source conditions	View language. enum: VI, EN
`view.callbackUrl`	string	Optional / source conditions	Registered callback URL. format: uri
`view.redirectUrl`	string	Optional / source conditions	Registered redirect URL. format: uri
`view.fontSize`	string	Optional / source conditions	UI font-size configuration.
`view.templateUiId`	string	Optional / source conditions	UI template identifier.
`view.expiresIn`	integer	Optional / source conditions	Units/meaning require confirmation; no default provided.

Illustrative payload — Not executed against the service

{
  "credentialID": "DEMO_SIC_CREDENTIAL",
  "numSignatures": 1,
  "documentDigests": {
    "hashes": [
      "ypeBEsobvcr6wjGzmiPcTaeG7/gUfE5yuYB3ha/uSLs="
    ],
    "hashAlgorithmOID": "2.16.840.1.101.3.4.2.1"
  }
}

Response · 202

Read HTTP status and business outcome separately.

Response 202
Field	Type	Presence	Description
`token`	string	Required	Token returned by the preceding step; do not publish it.

Response · default

Read HTTP status and business outcome separately.

Response default
Field	Type	Presence	Description
`code`	string	Optional / source conditions	Service error code, distinct from HTTP status.
`message`	string	Optional / source conditions	Short error message.
`description`	string	Optional / source conditions	Detailed explanation when present.

Next action

Persist the token, use the confirmed authorization view, then call authorizeCheck.

POST/v2/credentials/authorizeCheck

Read authorization outcome

Source documented · Deployment contract unconfirmed · Sandbox not tested

OperationId: SicAuthorizeCheck · Trusted SIC 1.7.260928 · PDF pages: 32, 33

Source-derived; deployment remains unconfirmed. Sample inputs are for reading, not live submission.

Preconditions and authentication

Have the token returned by authorize. Distinguish processing from available authorization data; source field conditions need confirmation. Keep the Bearer token server-side; exclude tokens/SAD from frontend code and public logs.

Request · application/json

Request schema
Field	Type	Presence	Description
`token`	string	Required	Token returned by the preceding step; do not publish it.

Illustrative payload — Not executed against the service

{
  "token": "DEMO_AUTHORIZATION_TOKEN"
}

Response · 200

Read HTTP status and business outcome separately.

Response 200
Field	Type	Presence	Description
`SAD`	string	Optional / source conditions	Signature Activation Data associated with the authorized content under the contract.
`credentialID`	string	Optional / source conditions	Credential identifier for the operation.
`expiresIn`	integer	Optional / source conditions	SAD lifetime in seconds in this table.
`token`	string	Optional / source conditions	If present, the source says processing continues; conditional field presence needs confirmation.

Response · default

Read HTTP status and business outcome separately.

Response default
Field	Type	Presence	Description
`code`	string	Optional / source conditions	Service error code, distinct from HTTP status.
`message`	string	Optional / source conditions	Short error message.
`description`	string	Optional / source conditions	Detailed explanation when present.

Confirmation required

SIC-02
SIC-06
SIC-09

Next action

Proceed only after obtaining valid authorization data under the contract.

POST/v2/signatures/signHash

Sign authorized hashes

Source documented · Deployment contract unconfirmed · Sandbox not tested

OperationId: SicSignHash · Trusted SIC 1.7.260928 · PDF pages: 36, 37, 38

Source-derived; deployment remains unconfirmed. Sample inputs are for reading, not live submission.

Preconditions and authentication

Have a contract-valid SAD for the credential and matching digests. Do not alter content after authorization; confirm signAlgo and signing mode. Keep the Bearer token server-side; exclude tokens/SAD from frontend code and public logs.

Request · application/json

Request schema
Field	Type	Presence	Description
`credentialID`	string	Required	Credential identifier for the operation.
`SAD`	string	Required	Signature Activation Data associated with the authorized content under the contract.
`hashes`	string[]	Required	Authorized digests; do not change the content.
`hashAlgorithmOID`	string	Required	Hash algorithm OID; select using confirmed configuration.
`signAlgo`	string	Required	Signature algorithm OID, mandatory in the table but absent in its example.
`operationMode`	string	Optional / source conditions	A: Asynchronous; S: synchronous, default S in signHash. Do not apply this default to issue. enum: A, S; default: S
`clientInfo`	object	Optional / source conditions
`clientInfo.application`	string	Optional / source conditions	Originating application name.
`validityPeriod`	integer	Optional / source conditions	Outcome retention duration in milliseconds according to the table.

Illustrative payload — Not executed against the service

{
  "credentialID": "DEMO_SIC_CREDENTIAL",
  "SAD": "DEMO_SAD_NOT_A_SECRET",
  "hashes": [
    "ypeBEsobvcr6wjGzmiPcTaeG7/gUfE5yuYB3ha/uSLs="
  ],
  "hashAlgorithmOID": "2.16.840.1.101.3.4.2.1",
  "signAlgo": "1.2.840.113549.1.1.11"
}

Response · 200

Read HTTP status and business outcome separately.

Response 200
Field	Type	Presence	Description
`signatures`	string[]	Optional / source conditions	Base64 signatures when completed.
`responseID`	string	Optional / source conditions	Signing outcome handle; see the source example conflict with requestID.

Response · default

Read HTTP status and business outcome separately.

Response default
Field	Type	Presence	Description
`code`	string	Optional / source conditions	Service error code, distinct from HTTP status.
`message`	string	Optional / source conditions	Short error message.
`description`	string	Optional / source conditions	Detailed explanation when present.

Confirmation required

SIC-02
SIC-04
SIC-10

Next action

Receive signatures or a handle under the confirmed mode, then assemble and validate the document.

POST/v2/signatures/signPolling

Poll an asynchronous signing outcome

Source documented · Deployment contract unconfirmed · Sandbox not tested

OperationId: SicSignPolling · Trusted SIC 1.7.260928 · PDF pages: 38, 39

Source-derived; deployment remains unconfirmed. Sample inputs are for reading, not live submission.

Preconditions and authentication

Have the asynchronous signing handle. Settle responseID/requestID before deployment. Polling does not create another signature. Keep the Bearer token server-side; exclude tokens/SAD from frontend code and public logs.

Request · application/json

Request schema
Field	Type	Presence	Description
`responseID`	string	Required	Signing outcome handle; see the source example conflict with requestID.

Illustrative payload — Not executed against the service

{
  "responseID": "DEMO_SIGN_RESPONSE"
}

Response · 200

Read HTTP status and business outcome separately.

Response 200
Field	Type	Presence	Description
`signatures`	string[]	Optional / source conditions	Signatures returned when creation completes.

Response · default

Read HTTP status and business outcome separately.

Response default
Field	Type	Presence	Description
`code`	string	Optional / source conditions	Service error code, distinct from HTTP status.
`message`	string	Optional / source conditions	Short error message.
`description`	string	Optional / source conditions	Detailed explanation when present.

Confirmation required

SIC-02
SIC-08

Next action

Confirm responseID versus requestID before integration; polling does not mean recreating the request.

POST/v2/credentials/info

Read credential information

Source documented · Deployment contract unconfirmed · Sandbox not tested

OperationId: SicCredentialInfo · Trusted SIC 1.7.260928 · PDF pages: 26, 27, 28, 29

Source-derived; deployment remains unconfirmed. Sample inputs are for reading, not live submission.

Preconditions and authentication

Have the credentialID to inspect. Select certificate/authorization detail level; certificate state is not document validation. Keep the Bearer token server-side; exclude tokens/SAD from frontend code and public logs.

Request · application/json

Request schema
Field	Type	Presence	Description
`credentialID`	string	Required	Credential identifier for the operation.
`certificates`	string	Optional / source conditions	Certificate-chain return selection. enum: none, single, chain; default: single
`certInfo`	boolean	Optional / source conditions	Request certificate details.
`lang`	string	Optional / source conditions	Language in the credential-information table; no enum stated.
`authInfo`	boolean	Optional / source conditions	Request authorization-mechanism details.

Illustrative payload — Not executed against the service

{
  "credentialID": "DEMO_SIC_CREDENTIAL",
  "certificates": "chain",
  "certInfo": true
}

Response · 200

Read HTTP status and business outcome separately.

Response 200
Field	Type	Presence	Description
`description`	string	Optional / source conditions	Localized credential description, maximum 255 characters in the table.
`signatureQualifier`	string	Optional / source conditions	Source signature qualifier.
`key`	object	Required	Object from source tables.
`key.status`	string	Required	Signing-key status. enum: Enabled, disabled
`key.algo`	string[]	Required	Supported key-algorithm OIDs.
`key.len`	integer	Required	Key length in bits.
`key.curve`	string	Optional / source conditions	Curve OID, conditional on ECDSA in the table.
`cert`	object	Optional / source conditions	Object from source tables.
`cert.status`	string	Optional / source conditions	Certificate state when the response is generated; no enum inferred.
`cert.certificates`	string[]	Optional / source conditions	Base64 chain, conditional on certificates=none/single/chain.
`cert.issuerDN`	string	Optional / source conditions	UTF-8 issuer DN under RFC 4514 when certificate information is requested.
`cert.serialNumber`	string	Optional / source conditions	Hex serial number when certInfo=true.
`cert.subjectDN`	string	Optional / source conditions	UTF-8 subject DN under RFC 4514 when certificate information is available.
`cert.validFrom`	string	Optional / source conditions	Validity start encoded as GeneralizedTime in the source.
`cert.validTo`	string	Optional / source conditions	Validity end encoded as GeneralizedTime in the source.
`auth`	object	Optional / source conditions	Object from source tables.
`auth.mode`	string	Optional / source conditions	Returned authorization mechanism; no scopes inferred. enum: Explicit, oauth2code
`auth.expression`	string	Optional / source conditions	Expression combining authentication objects.
`auth.objects`	object	Optional / source conditions	Object from source tables.
`SCAL`	string	Optional / source conditions	1: Source describes no hash/SAD binding; 2: binding present. Check actual configuration. enum: 1, 2
`multisign`	string	Required	Table specifies String; example uses a number. Confirm the type. Value represents maximum signatures.
`lang`	string	Optional / source conditions	Response language.

Response · default

Read HTTP status and business outcome separately.

Response default
Field	Type	Presence	Description
`code`	string	Optional / source conditions	Service error code, distinct from HTTP status.
`message`	string	Optional / source conditions	Short error message.
`description`	string	Optional / source conditions	Detailed explanation when present.

Confirmation required

SIC-02
SIC-12

Next action

Check credential, certificate and authorization mechanisms before signing.

Source function catalog

Specification functions
Function	Method / path	PDF page	Page coverage
Auth login	`POST /v2/auth/login`	7	Source catalog; schema not fully transcribed
Auth revoke	`POST /v2/auth/revoke`	9	Source catalog; schema not fully transcribed
Providers	`POST /v2/credentials/providers`	10	Source catalog; schema not fully transcribed
Signing package: PackageInfo	`POST /v2/credentials/providers`	10	Source catalog; schema not fully transcribed
Issue	`POST /v2/credentials/issue`	15	Source catalog; schema not fully transcribed
Issue check	`POST /v2/credentials/issueCheck`	19	Source catalog; schema not fully transcribed
List	`POST /v2/credentials/list`	21	Source catalog; schema not fully transcribed
Information	`POST /v2/credentials/info`	26	Read schema here
Authorize	`POST /v2/credentials/authorize`	30	Read schema here
Authorize check	`POST /v2/credentials/authorizeCheck`	32	Read schema here
Credential history	`POST /v2/credentials/history`	33	Source catalog; schema not fully transcribed
Sign hash	`POST /v2/signatures/signHash`	36	Read schema here
Sign polling	`POST /v2/signatures/signPolling`	38	Read schema here
Signing history	`POST /v2/signatures/history`	39	Source catalog; schema not fully transcribed
Owner management	`POST /v2/owner/management`	42	Source catalog; schema not fully transcribed

Items to settle before integration

SIC-01 · SIC issue p.15 / signHash p.37

Issue operationMode S/A differs from signHash.

No issuance example with an assumed default processing mode.

SIC-02 · SIC list pp.21,24–26; operations

The source uses both /v2 and /csc/v2.

Displayed paths follow tables; confirm deployment namespace.

SIC-03 · SIC providers p.10 / package p.12

Signing Package uses the providers path and packageInfo.

Confirm whether this is one operation with a data selection option.

SIC-04 · SIC signHash pp.37–38

SignAlgo is mandatory in the table but absent in the example.

Edited example includes signAlgo; the source OID is illustrative.

SIC-05 · SIC issueCheck p.19; views p.6

IssueCheck token origin and legacy API references in views need clarification.

Do not publish a runnable view/issue journey before confirmation.

SIC-06 · SIC authorizeCheck p.32 / callback pp.44–46

SAD has two different expansions.

Use Signature Activation Data for authorization guidance and record the source difference.

SIC-07 · SIC authorize p.30

View.expiresIn is Integer but example units are ambiguous.

Do not add defaults or operational time limits.

SIC-08 · SIC signPolling pp.38–39

Table specifies responseID; example specifies requestID.

Table-based request is read-only; execution remains disabled.

SIC-09 · SIC authorizeCheck pp.32–33

Conditional token/SAD presence and processing state are unclear.

Do not treat every HTTP 200 as completed authorization.

SIC-10 · SIC signHash pp.37–38

Conditional signatures/responseID presence per mode requires confirmation.

Do not invent production oneOf branches or state enums.

SIC-11 · SIC callback pp.44–54

Callback examples contain syntax/field/status inconsistencies; legacy scope is unclear.

Describe responsibilities; runnable payloads await corrections.

SIC-12 · SIC info pp.29–30

Multisign is String in the table but numeric in the example.

Retain table type for review, without claiming a confirmed schema.