Get the VeriFactu configuration of a company

The envelope every successful JSON response of the BeeL. API is wrapped in. There are no bare resources in v1 and none are planned: the payload always hangs off data.

• A single resource is an object in data.
• A collection hangs off a named key inside data, together with its pagination, also inside data — data: {invoices: [...], pagination: {...}}.
• A collection carries pagination unless its operation declares itself a closed catalogue: a fixed, bounded list with nothing to page through. The declaration is explicit in the operation; a missing pagination is never something to infer.
• GET /v1/accounts pages by cursor (data: {accounts: [...], next_cursor}). It is a documented variant of pagination, not another envelope.

Putting the array straight into data with pagination as its sibling is the shape a v2 would adopt; v1 is not being flipped to it.