---
title: "Retrieve a team's settings"
method: GET
path: "/api/v1/teams/{id}/settings"
tags: ["Teams"]
---

# Retrieve a team's settings

`GET /api/v1/teams/{id}/settings`

Required scope: `teams:read` </br>Organization authorization: `supported`

## Path parameters

- `id` integer, required

## Response `200`

Settings for the team with the provided id

- TeamSettings
  - `teamId` integer, required — Id of the team these settings belong to
  - `customerType` string, nullable — Customer type of the team
  - `invoicePeriod` string, nullable — Invoicing period for the team
  - `invoiceWithdraw` boolean, required — Whether team balance is withdrawn via invoice
  - `invoiceDestinationCode` string, nullable — Destination code used on team invoices
  - `poNumber` string, nullable — Purchase order number applied to team invoices
  - `eanNumber` string, nullable — EAN/CIF number of the team
  - `partnerExternalId` string, nullable — External id assigned to the team by the partner
  - `joinCode` string, required — Code used to join the team
  - `selfRegisterChargeKeys` boolean, required — Whether members can self-register charge keys for this team
  - `autoAcceptInvitationRequests` boolean, required — Whether team join requests are accepted automatically
  - `autoGenerateChargePointGroups` boolean, required — Whether charge point groups are generated automatically for the team
  - `showMembersOnApp` boolean, required — Whether team members are shown in the app
  - `onboardingSteps` OnboardingStep[], nullable — The onboarding steps enabled for the team, as {step, config?} entries. Absent unless the feature is enabled for the operator.
    - `step` 'ADD_VEHICLE' | 'ADD_PAYMENT_METHOD' | 'ADD_RFID' | 'ADD_CHARGER' | 'ADD_TEAM_MEMBER' | 'SETUP_CHARGING_RULE' | 'SETUP_REIMBURSEMENT', required — The onboarding step key. Present in the list means the step is enabled for the team.
    - `config` 'scheduled' | 'smart', nullable — Optional per-step configuration, interpreted by the step. Only SETUP_CHARGING_RULE carries config today: one of `scheduled`, `smart`. Null/absent for all other steps.

## Other responses

- `400` — The request is invalid
- `401` — Consumer with provided credentials was not found
- `403` — Operator doesn't have access to resource
- `404` — Entity with the provided id was not found

---

[API](https://skmtc.net/monta/apis/monta-partner-api.md) · [All operations](https://skmtc.net/monta/apis/monta-partner-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/monta/monta-partner-api/revisions/517e18f11015/schema)