Ellipse Gradient for Header

SmartRecruiters Integration Guide

Connect SmartRecruiters recruiting data with enterprise applications through REST APIs, selected webhook notifications, scheduled workflows, and secure data transformation.

SmartRecruiters integration options at a glance

SmartRecruiters primarily integrates through REST APIs for Jobs, Candidates, Applications, Hiring Processes, Users, Departments, and related recruiting resources. Selected recruiting events can generate webhook-style notifications, which Martini can receive through an exposed API endpoint before retrieving the current resource from SmartRecruiters. Scheduled workflows support paginated synchronization and checkpoint-based reconciliation. Candidate documents and attachments can be transferred where the relevant endpoint and permissions are available. Authentication may use OAuth 2.0 or SmartRecruiters-issued API credentials, depending on the account and API product. Martini stores credentials securely, transforms JSON payloads, applies recruiting business rules, and delivers data to downstream APIs, databases, files, or messaging systems.

Integration pointSupported by SmartRecruiters?Common use casesHow Martini supports it
REST APIsYesRead and manage recruiting resources such as Jobs, Candidates, Applications, Users, Departments, and related workflow information where authorized.Martini can consume SmartRecruiters REST endpoints from workflows, transform JSON payloads, expose APIs backed by SmartRecruiters, and apply business rules before downstream writes.
Webhooks / outbound callbacksLimitedReceive notifications for selected recruiting events. Coverage, payload detail, delivery behavior, and subscription management depend on the SmartRecruiters API product and account configuration.Martini can expose an HTTP endpoint, validate and normalize notifications, retrieve the current resource, and invoke downstream workflows. Scheduled reconciliation can cover events not delivered by webhooks.
File / attachment APIsLimitedRetrieve candidate or application documents such as résumés and cover letters where the relevant resource endpoint and permissions support the required operation.Martini can retrieve metadata and binary content, validate file type and size, apply security policies, and transfer files to approved HR or document platforms.
AuthenticationYesAuthorize access using OAuth 2.0 or SmartRecruiters-issued API credentials, subject to the selected API product, tenant, scopes, and account configuration.Martini can use environment-specific authentication configuration and store client secrets, API keys, and refresh tokens in secure secrets rather than embedding them in workflows.
Scheduled synchronizationYesSynchronize paginated Jobs, Candidates, Applications, Users, or Departments and periodically reconcile data not covered by selected event notifications.Martini scheduler-triggered workflows can process every page, persist checkpoints after successful downstream processing, and retry failed pages without advancing state prematurely.
Bulk / asynchronous APIsNot confirmedA general-purpose SmartRecruiters bulk or asynchronous export facility was not verified; integrations should use paginated REST operations unless SmartRecruiters confirms a product-specific option.Martini can orchestrate paginated and batched workflow processing, but should not assume a SmartRecruiters bulk API exists.
Database / analytics accessNoDirect SmartRecruiters database access was not verified. Reporting and analytics integrations should use APIs, supported exports, or an approved reporting interface.Martini can load API-derived data into authorized databases or analytics destinations without requiring direct access to SmartRecruiters’ SaaS database.

How SmartRecruiters exposes data and business events

SmartRecruiters REST APIs

SmartRecruiters REST APIs provide the primary integration mechanism for recruiting resources, including Jobs, Candidates, Applications, Hiring Processes, Users, and Departments. List operations should be treated as paginated, and write operations depend on authorization and the relevant API product.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates to SmartRecruiters, calls the required REST endpoint, follows pagination, validates the response, maps JSON into a canonical model, applies recruiting rules, and writes the result to one or more target systems.

Implementation sequence

Authenticate with the configured SmartRecruiters authorization
Call the required REST resource endpoint
Process every page in the response
Validate and normalize the JSON payload
Apply status, privacy, and ownership rules
Write the mapped result to the target system and record the checkpoint

SmartRecruiters webhook notifications

SmartRecruiters supports webhook-style notifications for selected recruiting events. Notifications may contain a full object or only an identifier, and event coverage, delivery behavior, authentication, and subscription management must be confirmed for the account and API product.

Martini implementation pattern

Martini implementation pattern: expose a controlled HTTP endpoint, validate the incoming request, parse the event, retrieve the current Job, Candidate, or Application through the SmartRecruiters REST API, and process the resource idempotently. Scheduled reconciliation covers missed or unsupported events.

Implementation sequence

Receive the SmartRecruiters notification
Validate request authentication or signature requirements
Identify the event and source resource
Retrieve the current resource representation when necessary
Check the source identifier for duplicate processing
Invoke the downstream workflow and record the outcome

SmartRecruiters file and attachment APIs

Candidate and Application workflows can involve résumés, cover letters, and other documents. Attachment operations are conditional on the relevant endpoint, resource, authorization, file limits, and SmartRecruiters account configuration.

Martini implementation pattern

Martini implementation pattern: retrieve permitted attachment metadata and binary content, validate content type and size, avoid exposing document contents in logs, and transfer the file to an approved HR or document platform with source and destination correlation.

Implementation sequence

Confirm the attachment endpoint and required permissions
Retrieve attachment metadata and binary content
Validate file type, size, and security policy
Transfer the document to the approved destination
Store source and destination identifiers
Apply retention and exception handling rules

Common SmartRecruiters integration patterns

Pattern 1: Sync accepted candidates to an HR platform

When to use this pattern

Use this pattern when candidates or applications reaching an approved recruiting stage must enter an HR or onboarding process. It combines event-driven processing where available with scheduled reconciliation for completeness.

Integration direction
SmartRecruiters
Martini
Workday
Example Mapping
SmartRecruiters FieldCanonical FieldTarget Field
Candidate.idperson.sourceIdWorker.externalReference
Candidate.emailperson.emailWorker.primaryEmail
Application.statusapplication.stageHireProcess.status
Job.departmentorganization.departmentWorker.organization
Martini implementation pattern

Martini receives a selected notification or polls Applications on a schedule, retrieves the related Candidate and Job, verifies that the Application status represents an approved hiring milestone, maps the data, validates required HR fields, and upserts the target. Stable source IDs prevent duplicates, while transient failures are retried and unresolved records are routed to an exception process.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • validation
  • error handling

Pattern 2: Publish approved Jobs to a careers website

When to use this pattern

Use this pattern when approved SmartRecruiters Jobs must be published or updated on an external careers site, intranet, or workforce-planning application.

Integration direction
SmartRecruiters
Martini
Careers website
Example Mapping
SmartRecruiters FieldCanonical FieldTarget Field
Job.titleposition.titleopening.title
Job.descriptionposition.descriptionopening.description
Job.locationposition.locationopening.location
Job.statusposition.lifecycleStatusopening.status
Martini implementation pattern

A scheduled Martini workflow retrieves paginated Jobs and optionally responds to selected SmartRecruiters notifications. It filters by approval and publication rules, transforms localized and organizational fields, upserts the careers-site record, and handles closed or withdrawn Jobs explicitly. Failed pages or target responses are retried without advancing the synchronization checkpoint.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • conditional routing
  • checkpoint handling
  • retry processing

Pattern 3: Load recruiting data into analytics

When to use this pattern

Use this pattern when recruiting teams need historical views of Jobs, Applications, Candidates, Users, or Departments in an analytics store or reporting pipeline.

Integration direction
SmartRecruiters
Martini
Analytics store
Example Mapping
SmartRecruiters FieldCanonical FieldTarget Field
Application.idapplication.sourceIdfact_application.application_key
Application.statusapplication.statusfact_application.status
Job.idposition.sourceIddim_job.job_key
Department.nameorganization.namedim_department.department_name
Martini implementation pattern

Martini invokes SmartRecruiters list endpoints on a schedule, processes all pages, normalizes timestamps and status values, enriches Applications with Job and Department references, and writes the result to an authorized analytics destination. Checkpoints advance only after successful processing, with periodic reconciliation for missed events or changed records.

Martini capabilities used
  • scheduler triggers
  • pagination orchestration
  • data transformation
  • mapping
  • database or API writes
  • monitoring

Pattern 4: Transfer candidate documents securely

When to use this pattern

Use this pattern when permitted résumés, cover letters, or other Application documents must be transferred to an HR, onboarding, or document-management platform.

Integration direction
SmartRecruiters
Martini
Document platform
Example Mapping
SmartRecruiters FieldCanonical FieldTarget Field
Candidate.idcandidate.sourceIddocument.ownerReference
Application.idapplication.sourceIddocument.applicationReference
attachment.fileNamedocument.namefile.name
attachment.contentdocument.binaryContentfile.content
Martini implementation pattern

Martini retrieves attachment metadata and content only when the SmartRecruiters endpoint and permissions support the operation. It validates file type and size, applies privacy and retention rules, transfers the binary content, records both identifiers, and retries transient failures without creating duplicate documents.

Martini capabilities used
  • workflow orchestration
  • file handling
  • validation
  • secure configuration
  • data mapping
  • idempotency
  • error handling

Applications commonly integrated with SmartRecruiters

SmartRecruiters can be integrated with adjacent HR, identity, workflow, document, customer, and analytics products. The exact objects and direction depend on the target application’s APIs, account permissions, and ownership rules.

Application Scenario Direction Martini Pattern
Workday Transfer hired-candidate or recruiting information into employee lifecycle and HR processes. SmartRecruiters → Martini → Workday Martini receives selected SmartRecruiters events or runs a scheduled workflow, maps Candidates, Applications, and Jobs to Workday’s authorized model, applies hiring-stage rules, and retries transient failures with source-to-target ID tracking.
SAP SuccessFactors Synchronize candidate, requisition, and hiring information with a broader HCM environment. SmartRecruiters → Martini → SAP SuccessFactors A Martini workflow retrieves paginated recruiting data, normalizes status and organizational fields, validates required values, and writes approved changes to SAP SuccessFactors while preserving checkpoints and error records.
Salesforce Connect recruiting activity with referral, partner, account, or custom talent-management processes. SmartRecruiters → Martini → Salesforce Martini consumes SmartRecruiters REST responses, maps selected Candidates, Applications, or Jobs to Salesforce objects, applies privacy and deduplication rules, and optionally exposes an internal API for controlled updates.
ServiceNow Initiate onboarding, access, equipment, or service-management tasks after a hiring milestone. SmartRecruiters → Martini → ServiceNow Martini evaluates SmartRecruiters Application status, creates or updates ServiceNow records through its API, correlates both identifiers, and routes rejected or incomplete requests to an exception workflow.
Microsoft Entra ID Prepare identity provisioning after recruiting and HR approval has completed. SmartRecruiters → Martini → Microsoft Entra ID Martini sends approved hiring information through an HR or onboarding workflow, validates identity attributes, and invokes the authorized Entra ID process rather than provisioning directly from an unapproved recruiting status.
Jira Create recruiting operations, implementation, or exception tasks associated with jobs and hiring processes. SmartRecruiters → Martini → Jira A Martini workflow creates or updates Jira issues from selected SmartRecruiters events or reconciliation results, maps ownership and priority, and records issue identifiers for status correlation.
DocuSign Initiate electronic signing of offer or employment-related documents where the deployment supports that process. SmartRecruiters → Martini → DocuSign Martini retrieves permitted candidate or application document information, validates the signing payload, invokes DocuSign APIs, and returns signing status to an approved downstream process with secure document handling.
Tableau Combine recruiting data with workforce and hiring analytics. SmartRecruiters → Martini → Tableau Martini extracts paginated Jobs, Applications, Users, and Departments on a schedule, normalizes timestamps and statuses, loads an analytics store or supported ingestion endpoint, and records checkpoint and reconciliation results.

How to build a SmartRecruiters integration in Martini

Objective

Establish SmartRecruiters access using the authorization method permitted for the account and API product.

Instructions in Martini

  • Confirm the SmartRecruiters tenant, API product, scopes, and permissions
  • Configure OAuth 2.0 or provisioned API credentials
  • Store secrets and tokens in environment-specific Martini configuration
  • Test access against the required recruiting resources

Objective

Select event-driven, scheduled, or API-led execution based on SmartRecruiters event coverage and synchronization requirements.

Instructions in Martini

  • Use selected webhook notifications when the required event is available
  • Use a scheduler for paginated synchronization and reconciliation
  • Expose a Martini API when downstream systems need a controlled integration façade
  • Document event gaps and fallback polling behavior

Objective

Obtain complete SmartRecruiters resources while handling pagination and identifier-only notifications.

Instructions in Martini

  • Call the appropriate Jobs, Candidates, Applications, Users, Departments, or attachment endpoint
  • Process all pages before advancing synchronization state
  • Retrieve the current resource after a notification when the payload is incomplete
  • Persist a checkpoint only after successful downstream processing

Objective

Convert SmartRecruiters JSON and files into canonical and target-system models.

Instructions in Martini

  • Map stable SmartRecruiters identifiers to target keys
  • Normalize status, timestamps, locations, departments, and localized fields
  • Minimize sensitive candidate data copied to downstream systems
  • Validate required fields and preserve traceability identifiers

Objective

Control which recruiting changes are forwarded and how statuses and exceptions are interpreted.

Instructions in Martini

  • Define explicit Application and Job status mappings
  • Require approved hiring milestones before creating HR or onboarding data
  • Apply duplicate, consent, retention, and ownership rules
  • Route incomplete or ambiguous records to controlled exception handling

Objective

Deliver transformed data reliably and provide operational visibility into synchronization health.

Instructions in Martini

  • Upsert target records where supported
  • Transfer attachments only after file and permission validation
  • Retry throttling and transient server failures with controlled backoff
  • Monitor webhook failures, synchronization lag, rejected records, and checkpoints

Common SmartRecruiters data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
JobsSynchronize open positions, descriptions, locations, departments, hiring teams, status, and publication information.Careers websites, workforce planning applications, Workday, SAP SuccessFactors, analytics platformsMartini retrieves Jobs through REST APIs or scheduled workflows, maps status and publication fields, applies approval rules, and upserts target records using stable identifiers.
CandidatesTransfer candidate profiles and contact information into approved HR, onboarding, analytics, or document workflows.Workday, SAP SuccessFactors, Salesforce, onboarding platforms, analytics storesMartini validates permissions and required fields, minimizes sensitive data, normalizes candidate attributes, and applies duplicate prevention and retention rules.
ApplicationsSynchronize a candidate’s application, job relationship, status, and recruiting workflow information.HCM platforms, ServiceNow, analytics platforms, onboarding systemsMartini maps SmartRecruiters application statuses to explicit target statuses, applies hiring-stage business rules, and maintains source-to-target correlation IDs.
Hiring ProcessesRepresent configured recruiting stages and process metadata associated with Jobs or Applications.HCM platforms, workflow systems, analytics storesMartini normalizes stage values, validates permitted transitions, and routes only business-approved milestones to downstream workflows.
UsersSynchronize recruiters, hiring managers, coordinators, and other recruiting users.HCM platforms, Salesforce, analytics platforms, workflow systemsMartini maps user identifiers and organizational attributes while applying access, privacy, and downstream ownership rules.
DepartmentsClassify Jobs and recruiting activity by organizational structure.HCM platforms, workforce planning, analytics platforms, careers websitesMartini maintains department mappings, handles renamed or inactive values through business rules, and uses them to enrich Job and Application transformations.

Authentication and security considerations

Tenant and application authorization

SmartRecruiters access is limited by the authorized company or tenant, API product, scopes, and account permissions. Confirm the required access to Jobs, Candidates, Applications, Users, Departments, and attachments before implementation.

Credential protection

Martini should store OAuth client secrets, refresh tokens, API keys, and other credentials in environment-specific secrets rather than embedding them in workflows.

Recruiting data protection

  • Minimize candidate and application fields copied to downstream systems.
  • Restrict access to résumés, cover letters, contact details, and interview information.
  • Protect webhook endpoints using the authentication or signature requirements confirmed for the SmartRecruiters account.
  • Define retention, deletion, and audit behavior across all participating systems.

Operational considerations for SmartRecruiters integrations

Rate limits and pagination

Treat SmartRecruiters list endpoints as paginated and confirm tenant-specific request limits. Control concurrency, use backoff for HTTP 429 and transient 5xx responses, and process every page before advancing a checkpoint.

Events and reconciliation

Webhook-style notifications cover selected events and may contain only an identifier. Combine event processing with scheduled reconciliation, and confirm delivery retries, ordering, subscription management, and authentication requirements.

Idempotency and status mapping

Use stable SmartRecruiters identifiers and source-to-target mappings to prevent duplicate Candidates, Applications, Jobs, or documents. Maintain explicit mappings for open, closed, rejected, withdrawn, hired, and archived statuses.

Schema and attachment changes

Handle optional fields and custom recruiting stages defensively, monitor API version changes, and verify attachment endpoints, file limits, content types, and permissions before transferring documents.

Monitoring and testing

Monitor synchronization lag, failed pages, webhook errors, rejected records, retries, and checkpoint state. Log correlation IDs and resource identifiers without exposing unnecessary personally identifiable information.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond point-to-point calls

Martini coordinates SmartRecruiters API calls, webhook intake, pagination, enrichment, target writes, and reconciliation in maintainable workflows rather than scattering logic across scripts.

Reusable integration assets

Teams can expose controlled APIs, reuse authentication and transformation logic, and apply consistent validation, status mapping, idempotency, and exception handling across recruiting processes.

Operational control

Scheduled execution, checkpoints, retries, monitoring, and environment-specific secrets provide a stronger operational model for candidate, application, job, and document synchronization than isolated scripts.

Flexible enterprise delivery

Martini can map SmartRecruiters JSON and files to downstream APIs, databases, analytics stores, and messaging systems while allowing custom business logic where the recruiting process requires it.

Frequently asked questions

How can SmartRecruiters be integrated with enterprise systems?

SmartRecruiters is primarily integrated through REST APIs for Jobs, Candidates, Applications, Hiring Processes, Users, Departments, and related resources. Selected recruiting events can produce webhook-style notifications, while scheduled workflows support paginated synchronization and reconciliation. Authentication may use OAuth 2.0 or SmartRecruiters-issued API credentials depending on the account and API product.

Can Martini integrate with SmartRecruiters?

Yes. Martini can consume SmartRecruiters REST APIs, receive supported webhook-style notifications through an exposed API endpoint, process scheduled pagination, transform recruiting data, and deliver it to downstream APIs, databases, files, or messaging systems supported by the Martini environment.

Do I need a connector to integrate SmartRecruiters with Martini?

No dedicated SmartRecruiters connector is required. Martini can integrate using SmartRecruiters’ confirmed native mechanisms, primarily REST APIs, selected webhook notifications, supported attachment endpoints, and the applicable OAuth 2.0 or API credential model.

Is there any extra Lonti cost to integrate SmartRecruiters with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate SmartRecruiters. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from SmartRecruiters, cloud infrastructure, document storage, or other third-party systems depending on subscriptions, usage, and deployment model.

Which SmartRecruiters integration methods should an implementation use?

REST APIs are the primary and recommended mechanism for current integrations. Selected webhook-style notifications can provide event-driven processing, but coverage must be verified for the required events. Scheduled, paginated REST synchronization should be retained for reconciliation and unsupported event coverage. No SmartRecruiters GraphQL or SOAP API was verified.

Can Martini receive SmartRecruiters events and keep data synchronized?

Martini can receive supported SmartRecruiters webhook-style notifications through an API endpoint, retrieve the current resource when the event contains only an identifier, and process it idempotently. Because event coverage is selective, important Jobs, Candidates, and Applications should also have scheduled reconciliation and checkpoint management.

How does Martini map SmartRecruiters data and handle failures?

Martini maps SmartRecruiters JSON into canonical and target-specific models, including explicit mappings for Application and Job statuses, identifiers, organizational values, and timestamps. Workflows can validate data, apply business rules, upsert target records, retry throttling and transient failures, and route authentication, validation, duplicate, or unresolved records to controlled exception handling.

Can Martini expose an API façade for SmartRecruiters?

Yes. Martini can expose a controlled REST API backed by SmartRecruiters data, allowing internal consumers to use a stable contract while Martini handles authentication, resource retrieval, transformation, filtering, and business rules. This façade does not require direct database access to SmartRecruiters.

Related Martini documentation

APIs

Events

Workflows

Security

Operations

Connect SmartRecruiters with your enterprise systems

Use Martini to build secure, maintainable SmartRecruiters integrations for recruiting data, events, synchronization, and document workflows.

EXPLORE MARTINI
BOOK A DEMO