# Create NinjaOne

> POST /api/services/ninja-one on the Vigilbase One API.

Source: https://docs.vigilbase.com/one/api/reference/services/post-services-ninja-one

`POST https://one.vigilbase.com/api/services/ninja-one`

> Needs a recent sign-in: renewing a token doesn't count, and MCP sessions and API keys are always refused. See [changes that need a recent sign-in](https://docs.vigilbase.com/one/api#changes-that-need-a-recent-sign-in).

## Authorizations

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`. Organisation API keys can't call this endpoint: it needs a recent sign-in by a person.
- Permissions checked: `write:services`

## Body (application/json)

- `operationId` (string, required)
- `ninjaOrganizationId` (string)
- `createIfNotExists` (boolean): Default `false`.
- `organizationData` (object)
  - `name` (string, required)
  - `description` (string)
  - `nodeApprovalMode` (string): One of `AUTOMATIC`, `MANUAL`, `REJECT`.
  - `tags` (string[])

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`. API keys can't call this.
curl --request POST \
  --url 'https://one.vigilbase.com/api/services/ninja-one' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"operationId":"<uuid>","ninjaOrganizationId":"<string>","createIfNotExists":false,"organizationData":{"name":"<string>","description":"<string>","nodeApprovalMode":"AUTOMATIC","tags":["<string>"]}}'
```