docs.visena.com
Visena runs the daily practice of Norwegian audit, accounting and advisory firms — clients, engagements, hours, documents and compliance in one system. This is where we publish how to use it, and how to build on it.
Currently published · AML · Partner API v1
Using Visena
Anti-money-laundering work in Visena is one continuous record: the risk model your firm authors, the customer due diligence you carry out against it, and the trail that proves both — years later, to someone who was not there.
Building on Visena
# 1 · trade the credential for a token curl -X POST -u "acme-partner-3f9a:$CLIENT_SECRET" \ -d "grant_type=client_credentials" \ https://api.visena.example/acme/auth/api/v1/token # 2 · call the API curl -H "Authorization: Bearer PhVYGf3qK9…" \ "https://api.visena.example/acme/api/v1/en/person"
Two tracks: using Visena day to day, and building on it. Every page exists in English and Norwegian.
Using Visena · AML
The three surfaces that feed each other, who does what and where, and the vocabulary you will meet in the screens.
user/aml/ → SetupAML-konfig, section by section: factors, classes, service areas, controls, the NACE and country tables, recalculation triggers and versioning.
risk-model.html → SetupBuilding the form the customer signs: question types, sections, conditions and skip rules, answer validation, translations, import and export.
form-builder.html → SetupSection and question conditions in one place: the operators, expression trees and typed operands, the live condition preview, and how a skip rule decides what the customer is asked next.
conditions.html → Daily workAn onboarding cycle end to end: services, screening, dispatch, assessment and conclusion — plus moving a customer onto a newer model version.
customer-measures.html → Daily workEach step of the wizard in detail — services, screening, dispatch, assessment and conclusion — and what leaving one behind you freezes.
wizard-steps.html → Daily workThe portfolio list: the KPI strip, the table and its sorting, both filter surfaces, the detail panel with its four-eyes approval tab, and the company card.
risk-classification.html → Daily workThe firmakort’s AML-risiko tab: one company’s risk, its history and its open obligations, read from the same record the portfolio list summarises.
company-card.html → Daily workWhat the customer receives and sees: the email and its link, SMS notification, the portal itself, BankID signing, and the status track from Sendt through to Fullført.
kyc-portal.html → OperationsThe cycles that keep running — PER, HND, MAN and OFF — the assess-the-cycle workspace, the approval deep flow, appointing the responsible officer, and deviation alerts.
ongoing-monitoring.html → ReportingThe suspicious-activity report to Økokrim, the portfolio report, the Excel export, and country exposure under section 4.
reporting.html →Building on Visena · Partner API
What the Partner API makes possible — import at scale, export without friction, sync continuously, or put your own portal in front of it all.
partner/api/ → EvaluationArchitecture, the surface you get and the security model — written for the people who have to sign off on the integration.
technical-overview.html → GuideThe whole flow in three moves, what you need before you start, and a 60-second taste that returns a real record.
getting-started.html → GuideInstances, credentials, access tokens and scopes, plain versus on-behalf credentials, masked ids, and what the locale in the URL decides.
concepts.html → GuideCreate, list, revoke and rotate a credential, then exchange it for a token — with a screen-by-screen walkthrough of doing it the first time.
credentials.html → GuideThe anatomy of a URL, the headers every request carries, create, read, update — PUT against PATCH — delete, and the response conventions worth knowing.
requests.html → GuideOffset lists, a cursor walk for one consistent extract, time-windowed timelines for resuming a sync, and filters.
lists-and-sync.html → GuideThe RFC 9457 problem document, what to do about each status code, a retry policy that will not make things worse, and a quick diagnosis table.
errors.html → GuaranteeWhat a read-scoped token can and cannot do — and the 403 Forbidden that proves a read-only integration is unable to change anything.
read-only-access.html → GuideThe checklist before you point an integration at production, and how to reach us when something does not add up.
go-live.html → ReferenceEvery endpoint of the Partner API — requests, parameters, response shapes and error codes — one page per resource, from the live API contract.
reference/ →