How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

VCV Vacancy API

The vacancy API from VCV — 23 operation(s) for vacancy.

VCV Vacancy API is one of 17 APIs that VCV publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include vacancy. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 43 operations across 23 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version v3.

Requests are made against 3 base URLs: https://my.vcv.ai, https://my.vcv.ru, {hostname}.

43 operations 23 paths 14 schemas 7 DELETE20 GET8 PATCH8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://my.vcv.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

VCV Vacancy API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (token) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 43

Across 23 paths, the API surfaces 43 operations — 7 DELETE, 20 GET, 8 PATCH, 8 POST. Each is listed below with its method, path, parameters, and response codes.

vacancy 43
GET
/api/v3/vacancies
Get api vacancies
getApiV3Vacancies 13 params → 200
POST
/api/v3/vacancies
Create api vacancies
postApiV3Vacancies body → 200
DELETE
/api/v3/vacancies
Delete api vacancies
deleteApiV3Vacancies body → 200
PATCH
/api/v3/vacancies
Update api vacancies
patchApiV3Vacancies body → 200
GET
/api/v3/vacancies/{id}
Get api vacancies by id
getApiV3VacanciesById 3 params → 200
DELETE
/api/v3/vacancies/{id}
Delete api vacancies by id
deleteApiV3VacanciesById 1 param → 200
PATCH
/api/v3/vacancies/{id}
Update api vacancies by id
patchApiV3VacanciesById 1 param body → 200
GET
/api/v3/vacancy-permissions
Get api vacancy permissions
getApiV3VacancyPermissions 8 params → 200
POST
/api/v3/vacancy-permissions
Create api vacancy permissions
postApiV3VacancyPermissions 1 param body → 200
GET
/api/v3/vacancy-permissions/{id}
Get api vacancy permissions by id
getApiV3VacancyPermissionsById 2 params → 200
PATCH
/api/v3/vacancy-permissions/{id}
Update api vacancy permissions by id
patchApiV3VacancyPermissionsById 2 params body → 200
DELETE
/api/v3/vacancy-permissions/{id}
Delete api vacancy permissions by id
deleteApiV3VacancyPermissionsById 1 param → 200
GET
/api/v3/vacancy-competences
Get api vacancy competences
getApiV3VacancyCompetences 6 params → 200
POST
/api/v3/vacancy-competences
Create api vacancy competences
postApiV3VacancyCompetences 1 param body → 200
GET
/api/v3/vacancy-competences/{id}
Get api vacancy competences by id
getApiV3VacancyCompetencesById 2 params → 200
PATCH
/api/v3/vacancy-competences/{id}
Update api vacancy competences by id
patchApiV3VacancyCompetencesById 2 params body → 200
DELETE
/api/v3/vacancy-competences/{id}
Delete api vacancy competences by id
deleteApiV3VacancyCompetencesById 1 param → 200
GET
/api/v3/competence-views
Get api competence views
getApiV3CompetenceViews 4 params → 200
GET
/api/v3/competence-views/{id}
Get api competence views by id
getApiV3CompetenceViewsById 1 param → 200
GET
/api/v3/competence-levels
Get api competence levels
getApiV3CompetenceLevels 4 params → 200
GET
/api/v3/competence-levels/{id}
Get api competence levels by id
getApiV3CompetenceLevelsById 1 param → 200
GET
/api/v3/vacancy-modules
Get api vacancy modules
getApiV3VacancyModules 6 params → 200
GET
/api/v3/vacancy-modules/{id_module}/{vacancy_id}
Get api vacancy modules by id module by vacancy id
getApiV3VacancyModulesByIdModuleByVacancyId 3 params → 200
PATCH
/api/v3/vacancy-modules/{id_module}/{vacancy_id}
Update api vacancy modules by id module by vacancy id
patchApiV3VacancyModulesByIdModuleByVacancyId 2 params body → 200
GET
/api/v3/vacancy-stages
Get api vacancy stages
getApiV3VacancyStages 6 params → 200
GET
/api/v3/vacancy-stages/{id_module}/{vacancy_id}
Get api vacancy stages by id module by vacancy id
getApiV3VacancyStagesByIdModuleByVacancyId 3 params → 200
PATCH
/api/v3/vacancy-stages/{id_module}/{vacancy_id}
Update api vacancy stages by id module by vacancy id
patchApiV3VacancyStagesByIdModuleByVacancyId 2 params body → 200
POST
/api/v3/vacancies/{vacancy_id}/logo
Create api vacancies by vacancy id logo
postApiV3VacanciesByVacancyIdLogo 1 param body → 200
DELETE
/api/v3/vacancies/{vacancy_id}/logo
Delete api vacancies by vacancy id logo
deleteApiV3VacanciesByVacancyIdLogo 1 param → 200
GET
/api/v3/vacancy-landing-url-history
Get api vacancy landing url history
getApiV3VacancyLandingUrlHistory 7 params → 200
POST
/api/v3/vacancy-landing-url-history/validate
Create api vacancy landing url history validate
postApiV3VacancyLandingUrlHistoryValidate body → 200
GET
/api/v3/vacancy-landing-url-history/{id}
Get api vacancy landing url history by id
getApiV3VacancyLandingUrlHistoryById 1 param → 200
DELETE
/api/v3/vacancy-landing-url-history/{id}
Delete api vacancy landing url history by id
deleteApiV3VacancyLandingUrlHistoryById 1 param → 200
GET
/api/v3/response-status-email-templates
Get api response status email templates
getApiV3ResponseStatusEmailTemplates 8 params → 200
POST
/api/v3/response-status-email-templates
Create api response status email templates
postApiV3ResponseStatusEmailTemplates 1 param body → 200
GET
/api/v3/response-status-email-templates/{id}
Get api response status email templates by id
getApiV3ResponseStatusEmailTemplatesById 2 params → 200
DELETE
/api/v3/response-status-email-templates/{id}
Delete api response status email templates by id
deleteApiV3ResponseStatusEmailTemplatesById 1 param → 200
PATCH
/api/v3/response-status-email-templates/{id}
Update api response status email templates by id
patchApiV3ResponseStatusEmailTemplatesById 2 params body → 200
POST
/api/v3/response-status-email-templates/{id}/recovery
Create api response status email templates by id recovery
postApiV3ResponseStatusEmailTemplatesByIdRecovery 2 params → 200
GET
/api/v3/vacancy-email-template-remind
Get api vacancy email template remind
getApiV3VacancyEmailTemplateRemind 5 params → 200
POST
/api/v3/vacancy-email-template-remind
Create api vacancy email template remind
postApiV3VacancyEmailTemplateRemind body → 200
GET
/api/v3/vacancy-email-template-remind/{id}
Get api vacancy email template remind by id
getApiV3VacancyEmailTemplateRemindById 1 param → 200
PATCH
/api/v3/vacancy-email-template-remind/{id}
Update api vacancy email template remind by id
patchApiV3VacancyEmailTemplateRemindById 1 param body → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ResponseStatus (13 properties), User (9 properties), RemindEmail (8 properties), ResponseStatusEmailTemplate (8 properties). Each schema is shown below with its type and property counts.

ResponseStatus
object
13 properties
Vacancy
object
7 properties
VacancyModuleStage
object
6 properties
CompetenceLevel
object
4 properties
Permission
object
5 properties
VacancyUrlHistory
object
3 properties
ResponseStatusEmailTemplate
object
8 properties
User
object
9 properties
RemindEmail
object
8 properties
Language
object
4 properties
Country
object
4 properties
CompetenceView
object
2 properties
VacancyModule
object
4 properties
VacancyCompetence
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vcv-vacancy-api-openapi.yml Raw ↑

Other APIs VCV publishes across the network.

VCV Chatbot API
VCV Companies API
VCV Countries API
VCV Enumeration API
VCV Integration API
VCV Interview API
VCV Invite API
VCV Languages API
VCV Limits API
VCV Response API
VCV Survey API
VCV Tags API
Where this information came from

This is an independent, third-party profile of VCV Vacancy API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.