canonical: https://jentic.com/apis/smartrecruiters.com/smartrecruiters

# Smartrecruiters Webhooks

SmartOnboard Public API. The API exposes 234 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically create a new candidate application, get candidate status. Covers 234 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a New Candidate Application
- Get candidate status
- Add comment to given approval request
- Query and filter Webhooks records by parameters
- Monitor Webhooks operational status and events

## Use cases

### Developer Tools Operations

Use the Webhooks to perform developer tools operations programmatically. The API provides 234 endpoints covering core functionality including create a new candidate application, get candidate status, get application configuration for posting.

Example prompt: Call POST /postings/{uuid}/candidates to create a new candidate application

### Automated configuration Management

Automate configuration operations by combining multiple Webhooks endpoints. Agents can get candidate status and then get application configuration for posting in a single workflow.

Example prompt: Call GET /postings/{uuid}/candidates/{candidateId}/status to get candidate status, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Webhooks 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 apiKey, oauth2 tokens manually.

Example prompt: Search Jentic for 'create a new candidate application', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /postings/{uuid}/candidates | Create a New Candidate Application |
| GET | /postings/{uuid}/candidates/{candidateId}/status | Get candidate status |
| GET | /postings/{uuid}/configuration | Get application configuration for posting |
| GET | /approvals/{approvalRequestId} | Get approval request by id |
| POST | /approvals/{approvalRequestId}/comments | Add comment to given approval request |
| GET | /approvals/{approvalRequestId}/comments | Get comments for given approval request |
| POST | /approvals | Create approval request |
| GET | /approvals | Get pending approvals requests where you are an approver. |

## Key resources

- **configuration** — Operations related to configuration
- **candidates** — Operations related to candidates
- **jobs** — Operations related to jobs
- **users** — Operations related to users
- **offers** — Operations related to offers

## Why Jentic

- **Setup:** Wiring SmartRecruiters Webhooks by hand means choosing between its x-smarttoken key and OAuth2 flows against the webhooks-api host and managing retries yourself. Through Jentic you install once, import the SmartRecruiters Webhooks API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** SmartRecruiters puts the posting and approval id in the URL path (/postings/{uuid}/..., /approvals/{approvalRequestId}), so a rule can pin your agent to one posting: it can add candidates and read their status. You choose the operations it may call, so approval creation is not included unless you add it.
- **Credential handling:** Your SmartRecruiters credential 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 'apply a candidate to a posting' or 'check a candidate's status', and Jentic returns the matching SmartRecruiters operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Webhooks use?

The Webhooks uses apiKey, oauth2 authentication. 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 a new candidate application with the Webhooks?

Yes. Use the POST /postings/{uuid}/candidates endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Webhooks?

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 a new candidate application through Jentic?

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

### How many endpoints does the Webhooks have?

The Webhooks exposes 234 endpoints covering configuration, candidates, jobs operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SmartRecruiters operations and credentials the agent may use. SmartRecruiters puts the posting and approval id in the URL path, such as /postings/{uuid}/candidates and /approvals/{approvalRequestId}, so a rule can pin the agent to a single posting where it can add candidate applications and read their status. Since you choose the operations it may call, actions like creating approval requests stay off limits unless you explicitly allow them.