# Create qualification

> POST /api/qualification on the Vigilbase One API.

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

`POST https://one.vigilbase.com/api/qualification`

## 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 acts for a signed-in person or changes how people sign in.

## Body (application/json)

- `companyName` (string, required): Min length 1.
- `domain` (string, required): Min length 1.
- `contactEmail` (string, required)
- `contactPhone` (string, required): Min length 1.
- `firstName` (string, required): Min length 1.
- `lastName` (string, required): Min length 1.
- `industry` (string, required): Min length 1.
- `employeeCount` (string, required): Min length 1.

## 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/qualification' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"companyName":"<string>","domain":"<string>","contactEmail":"<string>","contactPhone":"<string>","firstName":"<string>","lastName":"<string>","industry":"<string>","employeeCount":"<string>"}'
```