canonical: https://jentic.com/apis/stafiz.net/stafiz

# Stafiz API

Stafiz API for staff management, scheduling, and workforce optimization. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically create employee, list employees. Covers 13 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Create employee
- List employees
- Get employee
- Update employee
- Delete employee

## Use cases

### HR and Recruiting Operations

Use the Stafiz API to perform hr recruiting operations programmatically. The API provides 13 endpoints covering core functionality including create employee, list employees, get employee.

Example prompt: Call POST /employees to create employee

### Automated employees Management

Automate employees operations by combining multiple Stafiz API endpoints. Agents can list employees and then get employee in a single workflow.

Example prompt: Call GET /employees to list employees, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stafiz API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create employee', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/employees` | Create employee |
| GET | `/employees` | List employees |
| GET | `/employees/{employeeId}` | Get employee |
| PUT | `/employees/{employeeId}` | Update employee |
| DELETE | `/employees/{employeeId}` | Delete employee |
| POST | `/schedules` | Create schedule |
| GET | `/schedules` | List schedules |
| GET | `/schedules/{scheduleId}` | Get schedule |

## Key resources

- **employees** — Employee management
- **schedules** — Schedule management
- **shifts** — Shift management
- **time-tracking** — Time tracking and attendance

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/stafiz.net/stafiz/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Stafiz API by hand means learning its bearer auth against stafiz.net/api/v1 and threading the employee and schedule ids into paths yourself. Through Jentic you install once, import the Stafiz API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Stafiz puts the employee id in the URL path (`/employees/{employeeId}`), so a rule can pin your agent to reading a single employee. You choose the operations it may call, so ones like updating or deleting an employee are not included unless you add them.
- **Credential handling:** Your Stafiz bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list employees' or 'get an employee's schedule', and Jentic returns the matching Stafiz operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Stafiz API use?

The Stafiz API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create employee with the Stafiz API?

Yes. Use the POST /employees endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Stafiz API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create employee through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create employee'. Jentic returns the matching Stafiz API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stafiz API have?

The Stafiz API exposes 13 endpoints covering employees, schedules, shifts operations.

### Can I limit what my agent is allowed to do with the Stafiz API?

Yes. Because you run Jentic One yourself, your own rules decide which Stafiz operations and credentials the agent may use. Stafiz puts the employee id in the URL path (`/employees/{employeeId}`), so a rule can pin your agent to reading a single employee rather than listing everyone. You choose the operations it may call, so write actions like updating or deleting an employee stay out of reach unless you add them.