---
title: "Bulk-enable app onboarding across teams"
method: POST
path: "/api/v1/teams/onboarding-steps/bulk"
tags: ["Teams"]
---

# Bulk-enable app onboarding across teams

`POST /api/v1/teams/onboarding-steps/bulk`

Apply the same onboarding-step set to many teams in one call, equivalent to calling `PATCH /teams/{id}` with `onboardingSteps` for each. The response reports the outcome per team; a team the caller can't access is reported as failed rather than failing the whole batch.</br></br>Required scope: `teams:write` </br>Organization authorization: `supported`

## Request body

- BulkTeamOnboarding
  - `teamIds` integer[], required — Ids of the teams to apply the onboarding steps to. Duplicates are ignored.
  - `onboardingSteps` OnboardingStep[], required — The onboarding steps to enable for every listed team, as {step, config?} entries. Applied identically to each team; the list replaces that team's full enabled set, so an empty list clears onboarding for the team.
    - `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.

## Response `200`

Per-team onboarding outcome

- BulkTeamOnboardingResult — unresolved $ref

## 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)