Back office
Run TrustWix from inside your own admin, with your own staff and your own interface
You can build the whole of TrustWix into your own back office: your team never opens our console, and your customer records, your verifications and your review queue all live on one screen.
The two halves, and only one of them needs setup
This is the thing worth understanding before you write any code, because it decides how much work you are signing up for.
Reading needs nothing but an API key. Pulling verifications into your own database, showing a customer's status on their record, building a report, running a nightly export: all of that is the ordinary API, it has always worked, and there is nothing here to configure. Use a read-only key and it cannot change anything by accident.
Deciding needs a person. The moment one of your staff approves or rejects somebody, we have to record who. "Your server approved 4,000 people" is no use to a regulator, and no use to your own support team when a customer asks why they were turned down. So decisions are made as a seat: a real member of your TrustWix team, with the permissions your owner gave them.
Most integrations only need the first half
If you are syncing data into your own systems and your team still works the queue in our console, stop here. Take a read-only key and use the API reference. Everything below is for putting the decision itself in your interface.
How the second half fits together
Your owner maps your people to seats. On the Team page, each member gets your user id next to their name. That is the whole of the setup. See Sessions.
Your server exchanges its key for a session. It tells us which of your people is acting, and gets a short-lived token back. This happens on your server, never in a browser.
Your back office acts as that person. Their permissions are the ones your owner set. Their decisions are recorded under their name, in the same audit trail as the console.
The permissions, the environments and the flow access an owner configures on the Team page govern your back office exactly as they govern our console. There is no second place to configure any of it, and taking a permission away takes it away everywhere, on the next request.