API Reference
Monta.com

Bulk invite team members

post
https://partner-api.monta.com/api/v1/team-members/bulk

Invite multiple users to the same team in a single request. Each member is processed independently — a failure on one item does not abort siblings. The response is a list with one entry per input member, in order, indicating individual outcomes.

Required scope: team-members:write
Organization authorization: supported

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
int64
> 0

Id of the team that the members will be invited to. All members in the request are added to this team.

members
array of objects
required
length between 1 and 50

Members to invite to the team. Each item is processed independently — a failure on one member does not abort siblings. The response lists every input item with its individual outcome.

members*
int64 | null
> 0

Id of the user to be invited. When inviting by userId the fields email or phone must not be provided.

string | null

Email of the user to be invited. When inviting by email the fields userId or phone must not be provided.

string | null
^\+[1-9]\d{1,14}$

Phone of the user to be invited. When inviting by phone the fields userId or email must not be provided.

string
enum
required

Role for this member within the team

Allowed:
int64 | null

The price group for this team member, when not provided the default team price group will be applied

int64 | null

The cost group for this team member

int64 | null

The team member profile id to apply to this team member

boolean
Defaults to false

Indicates if the team member can configure charge points

boolean
Defaults to false

Gives the team member access to pay with the team wallet in the Monta shop (e.g. charge keys, stickers). Team wallet payment for charging sessions is controlled by teamWalletChargePaymentType

boolean
Defaults to false

Allows the team member to request sponsoring from this team

boolean
Defaults to false

Allows the team member to view and manage other members settings

string | null
enum
Defaults to none

On which chargers is the team member allowed to pay with Team Wallet?

all - On any charger (including roaming chargers)
 partner - On chargers with the same partner as this team
operator - On chargers with the same operator as this team
 team - On chargers belonging to this team
selected_operators - On chargers from selected operators
 none - The team member is not allowed to pay with Team Wallet for any charge session

Allowed:
boolean | null

Gives the team member permission to deposit to the team wallet

boolean | null

Gives the team member permission to withdraw from the team wallet

boolean | null

Gives the team member permission to manage charge keys for the team

canPayForChargesCountryIds
array of int32s | null

List of country ids for which the team member can pay for charges

canPayForChargesCountryIds
string | null

A note for the team member

chargePointIds
array of int64s | null

Ids of the charge points this team member will have access to

chargePointIds
string | null

External Id of this entity, managed by you.

partnerCustomPayload
object | null

Custom JSON payload for this entity, managed by you.
Note: the expected shape is a flat JSON object with named keys. The payload is limited to 1000 characters.

boolean
Defaults to true

Controls whether an invitation email and/or SMS is sent to the user based on the provided email and phone fields.

boolean | null
Defaults to false

Grants the invited member access to the team immediately, without waiting for them to accept the invitation.

number | null

Maximum price per kWh in the team currency that the team will cover when charging on AC.

number | null

Maximum price per kWh in the team currency that the team will cover when charging on DC.

Responses

Updated 2 months ago

Did this page help you?
Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 2 months ago

Did this page help you?