---
title: "Mandates (Minox)"
description: "Mandates"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/minox/Minox.MasterDataMandate.Mandates
original: https://documentation.invantive.eu/en/datamodels/minox/Minox.MasterDataMandate.Mandates
updated: 2026-11-01T16:19:41Z
license: https://documentation.invantive.eu/en/
---

# Mandates: Minox Mandates

`read only` `per partition` `REST`

- Catalog: `Minox`
- Schema: `MasterDataMandate`
- Label: Mandates

Search for mandates with filters in query.

The data in this table is partitioned per value of the `administration_code` column.

Can only retrieve data.

## API Source

- Endpoint: `/tenant/{tenant_id}/administration/{administration_id}/mandate`
- Operation: `get /tenant/{tenant_id}/administration/{administration_id}/mandate`

## Parameters

| Name | Data Type | Required | Default | Documentation |
|---|---|:---:|---|---|
| `active` | `` | [ ] |  | Only get mandates that are active or not. |
| `administration_code` | `` | [ ] |  | Partition to retrieve data from. |
| `customer_id` | `` | [ ] |  | Only get mandates for a single customer. |
| `next` | `` | [ ] |  | A single request returns a maximum of 400 mandates. In case more mandates have been found, a token will be provided. The next page can be accessed by providing this token to the next request. An example: GET /mandates?next=[token] where [token] is the provided token |

## Table Columns

The columns of the table `Mandates` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `active` | `char` | Active | [ ] | filters on the platform, writable, `active` |  |
| `authorization_type` | `varchar2` | Authorization Type | [ ] | filters on the platform, writable, `authorization_type` |  |
| `code` | `varchar2` | Code | [ ] | filters on the platform, writable, `code` |  |
| `collection_date` | `datetime` | Collection Date | [ ] | filters on the platform, writable, `collection_date` |  |
| `collection_type` | `varchar2` | Collection Type | [ ] | filters on the platform, writable, `collection_type` |  |
| `customer_id` | `int64` | Customer ID | [ ] | filters on the platform, writable, `customer_id` |  |
| `first_collection` | `char` | First Collection | [ ] | filters on the platform, writable, `first_collection` |  |
| `id` | `varchar2` | ID | [ ] | filters on the platform, writable, `id` |  |
| `serial_number` | `int64` | Serial Number | [ ] | filters on the platform, writable, `serial_number` |  |
| `signing_city` | `varchar2` | Signing City | [ ] | filters on the platform, writable, `signing_city` |  |
| `signing_date` | `datetime` | Signing Date | [ ] | filters on the platform, writable, `signing_date` |  |



## Release Notes

What changed per release in the tables, columns, attributes and capabilities of the driver:

- [Minox](/en/release-notes/drivers?driver=minox)

### Changes of This Table, 26.0 to 27.0

<a id="MNX-27.0-D187"></a><a id="MNX-27.0-D188"></a>

- `-` `administration_code`
- `-` `administration_name`

[All changes of the driver, 26.0 to 27.0](/en/release-notes/drivers?driver=minox&step=26.0-to-27.0#minox-26.0-to-27.0)

