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

Nayya Employees API

The Employees API from Nayya — 2 operation(s) for employees.

Nayya Employees API is one of 11 APIs that Nayya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Employees. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 0.1.

Requests are made against 2 base URLs: https://integrate.nayya.com/accounts, https://integrate.partners.nayya.com/accounts.

5 operations 2 paths 5 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1
Base URL
https://integrate.nayya.com/accounts
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — JWT token

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Employees 5
POST
/employers/{employerId}/employees
Create an Employee
create-employee 2 params body → 201400403404409422500
GET
/employers/{employerId}/employees
Get all Employees
list-employees 5 params → 200403404422500
GET
/employers/{employerId}/employees/{employeeId}
Get Employee by ID
get-employee-by-id 3 params → 200403404500
PATCH
/employers/{employerId}/employees/{employeeId}
Update Employee
update-employee 3 params body → 200400403404409422500
DELETE
/employers/{employerId}/employees/{employeeId}
Delete Employee
delete-employee 3 params → 204400403404409500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are EmployeeResponseDto (31 properties), CreateEmployeeDto (26 properties), UpdateEmployeeDto (25 properties), DependentResponseDto (23 properties). Each schema is shown below with its type and property counts.

CreateEmployeeDto
object
26 properties 4 required
ListEmployeesDto
object
4 properties 4 required
DependentResponseDto
object
23 properties 14 required
UpdateEmployeeDto
object
25 properties
EmployeeResponseDto
object
31 properties 25 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nayya-employees-api-openapi.yml Raw ↑

Other APIs Nayya publishes across the network.

Nayya Benefits API
Nayya Carriers API
Nayya Connections API
Nayya Dependents API
Nayya Employers API
Nayya Enrollments API
Nayya Recommendations API
Nayya Rule Templates API
Nayya Snapshots API
Nayya Token API
Where this information came from

This is an independent, third-party profile of Nayya Employees 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.