Get an AI analysis of a company's signatory rules

Enterprise+ tier

GEThttps://lens-api.tic.io/companies/{id}/signatory/analysis

The analysis interprets the company’s signatory rule (firmateckning) and lists the persons who can sign. The model reads the rule; whether an eligible person really is a current board member is decided by us afterwards, from the registered board, and returned in matchType.

Matching eligible persons to the board

`matchType`	Meaning	How to use it
`exact`	Tied to a current board member by identity number, and either eligible through their role (e.g. “styrelsen”, “verkställande direktören”) or named in the rule with a name that fits only that member.	Safe to treat as that board member.
`fuzzyName`	Tied to a current board member by identity number, but the name in the rule does not fit the member’s registered names (name change, spelling, middle names) or fits more than one member. The link is the model’s inference.	Show it, but let a person confirm it.
`unmatched`	Not tied to any current board member: no identity number, one that is not on the current board, or a birth date shared by several board members.	Do not treat as a board member.

nameInSignatoryText is the name exactly as written in the rule, or null when the person is eligible through their role only.

Identity numbers

identityNumberType says what personalIdentityNumber holds:

`identityNumberType`	Meaning
`personalIdentityNumber`	Swedish personnummer or samordningsnummer.
`birthDate`	Only a birth date (`YYYYMM`, `YYYYMMDD` or `YYYYMMDD0000`), which is what Bolagsverket registers for a person without a Swedish number, for example a Norwegian board member. Not unique - never use it alone as an identity.
`unknown`	Some other format.
`none`	No identity number.

personId is set only when the person is tied to a current board member.

Caching

The analysis is cached per signatory record and recomputed when the signatory text changes, or when we change how the analysis is made.

Authorization

x-api-keystringheaderrequired

Your API key, sent in the x-api-key header.

Path parameters

idintegerrequired

Internal company ID

format: int32

Responses

Signing authority analysis · application/json

companyIdinteger

format: int32

companySignatoryIdinteger | null

format: int32

signatureDescriptionstring | null

analysisSigningAuthorityAnalysis

Hide child attributes

summarystring | null

rulesSigningRule[] | null

Show child attributes

descriptionstring | null

typestring | null

requiredSignatoriesinteger | null

format: int32

requiredRolesstring[] | null

eligiblePersonsSigningEligiblePerson[] | null

Show child attributes

personIdinteger | null

format: int32

personalIdentityNumberstring | null

identityNumberTypestring

One of: none personalIdentityNumber birthDate unknown

namestring | null

nameInSignatoryTextstring | null

matchTypestring

One of: unmatched exact fuzzyName

rolesstring[] | null

canSignAloneboolean

applicableRulesstring[] | null

{ "companyId": 123, "companySignatoryId": 123, "signatureDescription": "<string>", "analysis": { "summary": "<string>", "rules": [ { "description": "<string>", "type": "<string>", "requiredSignatories": 123, "requiredRoles": [ "<string>" ] } ], "eligiblePersons": [ { "personId": 123, "personalIdentityNumber": "<string>", "identityNumberType": "none", "name": "<string>", "nameInSignatoryText": "<string>", "matchType": "unmatched", "roles": [ "<string>" ], "canSignAlone": true, "applicableRules": [ "<string>" ] } ] } }