Ellipse Gradient for Header

15Five Integration Guide

Connect 15Five employee engagement and performance data with HR, identity, analytics, and collaboration systems through REST API workflows.

15Five integration options at a glance

15Five provides a REST API for authorized programmatic access to people and performance-related data, including Users, Objectives, Key results, Check-ins, Reviews, and High Fives, subject to the current endpoint catalog and account permissions. API credentials or tokens should be confirmed against the current 15Five documentation and stored in Martini Secrets Management. Dedicated bulk, database, GraphQL, and SOAP interfaces were not confirmed. Broad webhook coverage is also unconfirmed, so scheduled REST synchronization with pagination, checkpoints, throttling, and retries is the dependable planning baseline. Martini can consume the API, transform payloads, apply business rules, and expose controlled APIs for downstream systems.

Integration pointSupported by 15Five?Common use casesHow Martini supports it
REST APIsYesRead Users, Check-ins, Reviews, Objectives, Key results, and High Fives, and perform supported write operations for account and people-related data.Martini can consume the 15Five REST API through HTTP-based workflow steps, map JSON payloads, validate data, and expose a separate API for downstream consumers.
AuthenticationLimitedAuthorized 15Five API access uses account-level API credentials or keys/tokens; the exact header format, lifecycle, and permissions require confirmation in the current reference.Martini can isolate credentials in environment-specific REST API configuration and Secrets Management rather than embedding them in workflows or mappings.
Scheduled synchronizationYesScheduled REST polling is the dependable baseline for employee, objective, key-result, check-in, and review synchronization when event delivery is unavailable or unconfirmed.Martini can trigger workflows on a schedule, maintain checkpoints, paginate requests, throttle calls, and retry transient failures.
Webhooks / outbound callbacksNot confirmed15Five webhook or callback coverage was not confirmed. Availability, event types, signing, retries, and delivery guarantees must be verified for the account and required resources.If 15Five provides the required callback, Martini can expose an API endpoint, validate the request, and start a workflow; otherwise it can use scheduled polling.
Bulk / async / batch APIsNot confirmedNo dedicated bulk or asynchronous API was confirmed. Large transfers should use paginated REST requests and controlled synchronization unless 15Five documents another option.Martini can orchestrate batches, checkpoints, concurrency limits, and replayable error handling around the confirmed REST interface.
File / attachment APIsNot confirmedA general-purpose file or attachment API was not confirmed for reviews, check-ins, or other 15Five objects.Martini can handle files when a supported 15Five endpoint is confirmed, but the transfer design should not assume attachment availability.
GraphQL APIsNot confirmedNo official 15Five GraphQL API documentation was confirmed, so GraphQL should not be assumed for this integration.Martini can consume GraphQL generally, but a 15Five GraphQL workflow should only be designed after an official endpoint is confirmed.
Database / analytics accessNoDirect database access was not identified as a supported 15Five integration mechanism.Martini should use the 15Five REST API and can then write normalized data to supported databases or analytics destinations.

How 15Five exposes data and business events

15Five REST APIs

REST is the primary confirmed 15Five programmatic integration mechanism. Authorized accounts can use the API to access people and performance-related data, although the current endpoint catalog, nesting, permissions, and write coverage should be verified before implementation.

Martini implementation pattern

Martini implementation pattern: a workflow calls the configured 15Five REST API, handles pagination and response validation, maps Users or performance objects into a canonical model, applies business rules, and writes to the target system. For inbound use cases, Martini can expose a controlled API that accepts normalized data and invokes supported 15Five operations.

Implementation sequence

Authenticate using the confirmed 15Five API credential format
Invoke the required 15Five REST resource
Follow documented pagination and store the synchronization checkpoint
Validate the response and map it to the target schema
Apply filtering and business rules for sensitive or incomplete data
Write or upsert the target record and persist reconciliation metadata

Scheduled 15Five synchronization

Because broad webhook and callback coverage was not confirmed, scheduled REST polling is the dependable approach for many 15Five integrations. It can support employee, objective, key-result, review, and check-in exchanges where the API exposes the required fields and filters.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow, which reads the last successful checkpoint, retrieves bounded or incremental pages, transforms each object, and writes results idempotently. The workflow records failures for replay and uses backoff for rate limits or temporary service errors.

Implementation sequence

Start the workflow on an approved schedule
Read the last successful checkpoint and synchronization boundaries
Retrieve paginated 15Five data within the selected scope
Map and validate each object before processing
Upsert the target using stable identifiers and duplicate protection
Store the new checkpoint and route failed items for replay

Common 15Five integration patterns

Pattern 1: Synchronize HR employees to 15Five Users

When to use this pattern

Use this pattern when Workday, BambooHR, or Rippling is the system of record for employee identity and organizational data. It supports hires, transfers, manager changes, and terminations while avoiding duplicate user creation.

Integration direction
Workday or BambooHR
Martini
15Five
Example Mapping
15Five FieldCanonical FieldTarget Field
employeeIdemployee.externalIdUsers.externalId
emailemployee.emailUsers.email
managerIdemployee.managerExternalIdUsers.managerId
employmentStatusemployee.statusUsers.status
Martini implementation pattern

A scheduled Martini workflow retrieves changed employees, matches them by a stable employee ID or email, validates manager and organizational references, and invokes supported 15Five user operations. It separates deactivation from deletion, records source identifiers, and retries transient failures without creating duplicates.

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

Pattern 2: Publish 15Five Objectives to analytics

When to use this pattern

Use this pattern when reporting teams need normalized Objectives and Key results in a warehouse or analytics platform. It is suited to scheduled or incremental extraction where 15Five exposes suitable timestamps or filters.

Integration direction
15Five
Martini
Analytics database
Example Mapping
15Five FieldCanonical FieldTarget Field
objectiveIdgoal.externalIdobjectives.source_id
objectiveNamegoal.nameobjectives.name
keyResultValuemeasure.currentValuekey_results.current_value
statusgoal.statusobjectives.status
Martini implementation pattern

Martini reads the durable checkpoint, retrieves paginated Objectives and related Key results, normalizes parent-child relationships, and upserts the analytics model. It preserves source IDs, rejects incomplete parent references, and advances the checkpoint only after successful writes.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • mapping and transformation
  • checkpointing
  • error handling

Pattern 3: Transfer approved performance data

When to use this pattern

Use this pattern when an HR or people-analytics system requires selected Review or Check-in information. It is appropriate for controlled exchanges that restrict confidential narrative fields and process only approved or completed data.

Integration direction
15Five
Martini
HR analytics platform
Example Mapping
15Five FieldCanonical FieldTarget Field
reviewStatusperformance.statusreview.status
revieweeIdperformance.personExternalIdreview.employee_id
completedAtperformance.completedAtreview.completed_at
departmentorganization.departmentreview.department
Martini implementation pattern

A Martini workflow retrieves supported Review or Check-in fields, filters by completion status, department, or region, removes free-text comments unless explicitly approved, and writes the reduced payload to the target. Validation failures are quarantined and transient API failures are retried.

Martini capabilities used
  • workflows
  • field-level filtering
  • data mapping
  • business rules
  • secure configuration
  • error handling

Pattern 4: Notify collaboration channels about selected changes

When to use this pattern

Use this pattern for approved recognition, objective, review, or check-in notifications in Slack or Microsoft Teams. Since broad 15Five event delivery is unconfirmed, the implementation should support scheduled polling unless the required callback is verified.

Integration direction
15Five
Martini
Slack or Microsoft Teams
Example Mapping
15Five FieldCanonical FieldTarget Field
highFiveMessagerecognition.messagenotification.text
userNamerecognition.senderNamenotification.sender
objectiveStatusgoal.statusnotification.summary
eventIdevent.externalIdnotification.deduplicationKey
Martini implementation pattern

Martini polls the relevant 15Five resources or receives a verified callback, filters events against notification policy, removes sensitive content, and sends a formatted message to the collaboration platform. Event IDs or object IDs prevent duplicate notifications, while failures are recorded for replay.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • conditional routing
  • data transformation
  • duplicate handling
  • error handling

Applications commonly integrated with 15Five

15Five can participate in enterprise workflows that keep employee data aligned with HR systems, publish performance information to analytics platforms, and deliver selected notifications to collaboration tools. Exact write operations, event coverage, and native application support should be confirmed for the relevant 15Five account.

Application Scenario Direction Martini Pattern
Workday Synchronize employee profiles, reporting relationships, departments, and employment status with 15Five. Workday → Martini → 15Five Run a scheduled Martini workflow that reads approved Workday changes, matches employees by stable identifiers, maps organizational fields, applies hire, transfer, and termination rules, and performs supported 15Five user operations with idempotent retry handling.
BambooHR Keep 15Five Users and organizational attributes aligned with BambooHR employee data. BambooHR → Martini → 15Five Consume BambooHR changes on a schedule, normalize employee and manager fields, validate required values, and create or update supported 15Five Users while recording source identifiers for reconciliation.
Rippling Provision or update 15Five users as employees join, leave, or change teams. Rippling → Martini → 15Five Use a scheduled workflow to retrieve Rippling employee changes, map identity and employment status fields, separate deactivation from deletion logic, and retry only transient 15Five API failures.
Slack Deliver selected recognition, check-in, review, or objective notifications in collaboration channels. 15Five → Martini → Slack Poll 15Five when callbacks are unavailable, filter approved events or status changes, remove sensitive content, and publish a controlled Slack notification with duplicate protection.
Microsoft Teams Surface approved performance or engagement notifications in organizations using Teams for collaboration. 15Five → Martini → Microsoft Teams Retrieve relevant 15Five changes through scheduled REST workflows, apply notification and confidentiality rules, transform the message format, and deliver it to the designated Teams endpoint.
Jira Relate team objectives or delivery progress to engineering work and project execution. Jira → Martini → 15Five Use Martini to mediate approved Jira project or progress data into 15Five Objectives or Key results where supported, with field validation, identifier mapping, and exception routing for unsupported structures.
Salesforce Combine approved employee or team performance information with business-unit reporting and operational analytics. 15Five → Martini → Salesforce Retrieve selected 15Five data, apply field-level filtering for sensitive performance information, map it to Salesforce reporting structures, and upsert using stable identifiers.
ServiceNow Coordinate approved organizational, manager, or employee data with service-management workflows and reporting. ServiceNow → Martini → 15Five Orchestrate a mediated exchange between ServiceNow and 15Five, validate the permitted employee fields, apply business rules for organizational changes, and route rejected records for review.

How to build a 15Five integration in Martini

Objective

Establish an environment-specific 15Five REST API configuration and protect the account credential.

Instructions in Martini

  • Confirm the current 15Five credential format, permissions, and endpoint requirements
  • Store credentials in Martini Secrets Management
  • Configure HTTPS API access without embedding secrets in workflow logic

Objective

Select a schedule or a verified callback based on the required 15Five capability.

Instructions in Martini

  • Use a Scheduler Trigger for polling and recurring synchronization
  • Use an API endpoint only if 15Five confirms the required webhook or callback
  • Define synchronization scope, frequency, and checkpoint policy

Objective

Read the required 15Five objects while respecting pagination and account limits.

Instructions in Martini

  • Call the relevant REST resources for Users, Objectives, Key results, Reviews, Check-ins, or High Fives
  • Implement documented pagination and bounded queries
  • Capture response metadata and the last successful synchronization position

Objective

Coordinate retrieval, validation, transformation, target writes, and exception paths in one maintainable workflow.

Instructions in Martini

  • Route records by object type or business process
  • Separate transient API failures from validation and authorization failures
  • Persist replay metadata without exposing sensitive performance content

Objective

Convert 15Five payloads into the canonical and target schemas required by HR, analytics, or collaboration systems.

Instructions in Martini

  • Map stable IDs, users, managers, objectives, statuses, dates, and relationships
  • Normalize values and handle nested resources according to the confirmed API model
  • Filter confidential comments and fields unless explicitly approved

Objective

Enforce organizational, privacy, lifecycle, and deduplication policies before writing data.

Instructions in Martini

  • Match users by stable employee or 15Five identifiers
  • Separate deactivation from deletion decisions
  • Restrict performance data by completion status, department, region, or approved field list

Common 15Five data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
UsersRepresent employees, managers, administrators, and other people in the 15Five account.Workday, BambooHR, Rippling, identity platforms, analytics systemsMartini matches stable employee or 15Five identifiers, maps manager and organizational fields, validates required values, and applies create, update, deactivation, and reconciliation rules.
Check-insCapture recurring employee-manager progress and engagement submissions.HR platforms, people analytics systems, reporting warehousesMartini retrieves approved fields, filters sensitive narrative content, maps status and ownership fields, and transfers only data required by the business process.
ReviewsRepresent formal performance review cycles and associated review information.HR platforms, people analytics systems, controlled reporting storesMartini can synchronize supported review fields, restrict transfers to completed or approved reviews, and avoid logging confidential comments or unnecessary personal data.
ObjectivesRepresent goals assigned to individuals, teams, or the organization.Analytics platforms, Jira, reporting warehouses, collaboration toolsMartini normalizes ownership, team, status, dates, and identifiers, then upserts objectives while preserving source IDs and handling rejected records.
Key resultsMeasure outcomes associated with Objectives.Analytics platforms, Jira, reporting warehousesMartini relates Key results to Objectives, converts values and statuses into the target model, validates parent references, and checkpoints successful synchronization.
High FivesRepresent recognition or peer feedback given to Users.Slack, Microsoft Teams, analytics platformsMartini can retrieve approved recognition data, apply confidentiality rules, deduplicate notifications, and publish only permitted fields to downstream systems.

Authentication and security considerations

Credential handling

15Five API access uses account credentials or API keys or tokens, but the exact header format, lifecycle, and permissions should be confirmed in the current 15Five reference. Martini should store these values in environment-specific Secrets Management and REST API configuration.

Least privilege and sensitive data

Reviews, Check-ins, feedback, and recognition can contain confidential employee information. Restrict credentials, fields, workflow access, and logs to the approved business purpose. Do not assume OAuth 2.0, JWT, or granular scopes unless 15Five confirms them.

Transport and API protection

Use HTTPS for API requests and validate any future callback authentication or signature mechanism before accepting events. Keep vendor credentials separate across development, test, and production environments.

Operational considerations for 15Five integrations

Rate limits and pagination

Confirm 15Five account limits and page-size behavior. Use pagination, bounded queries, limited concurrency, and backoff for HTTP 429 responses, respecting Retry-After when supplied.

Checkpoints and idempotency

Store durable synchronization checkpoints when updated timestamps or filters are available. Use stable object or employee identifiers for idempotent upserts and protect against replayed records or duplicate notifications.

Retries and failures

Retry temporary network, 5xx, and rate-limit failures with backoff. Route authentication, authorization, validation, stale-object, and permanent business-rule failures to an operational error path rather than retrying indefinitely.

Schema changes and testing

Validate required fields, tolerate additive fields where possible, preserve source identifiers, and version mappings when contracts change. Test pagination, empty responses, manager changes, review status transitions, revoked credentials, duplicate processing, and controlled test data.

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

Reusable orchestration

Martini separates 15Five API access from business workflows, allowing the same authenticated configuration, mappings, validation rules, and error paths to support HR, analytics, and collaboration use cases.

Controlled transformation

Instead of duplicating point-to-point scripts, Martini provides centralized mapping, filtering, enrichment, and business rules for Users, Objectives, Key results, Reviews, Check-ins, and High Fives.

Operational reliability

Workflows can combine scheduling, pagination, checkpoints, retries, idempotent writes, and monitoring. This provides a maintainable integration boundary without requiring direct database access or unsupported vendor mechanisms.

API-led access

Martini can expose a controlled API façade so downstream systems use a stable normalized contract while 15Five-specific credentials, schemas, and implementation changes remain within the integration layer.

Frequently asked questions

How can 15Five be integrated with enterprise systems?

15Five can be integrated through its confirmed REST API for authorized accounts. Enterprise workflows can retrieve Users, Objectives, Key results, Check-ins, Reviews, and High Fives, transform the data, and write it to HR, analytics, or collaboration systems. Scheduled synchronization is the dependable baseline because broad webhook, bulk, GraphQL, and SOAP support was not confirmed.

Can Martini integrate with 15Five?

Yes. Martini can consume the 15Five REST API through HTTP-based workflows, store credentials securely, paginate through responses, map and transform payloads, apply business rules, and write to downstream systems. If 15Five confirms the required callback capability, Martini can also receive those callbacks through an API endpoint.

Do I need a connector to integrate 15Five with Martini?

No. A dedicated 15Five connector is not required. Martini can integrate using 15Five's confirmed REST API and account credentials, with scheduled workflows or verified callbacks where available.

Is there any extra Lonti cost to integrate 15Five with Martini?

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

Which 15Five integration methods should architects use?

REST is the primary confirmed method and should be the foundation for new integrations. Use paginated and, where available, incremental REST requests for synchronization. GraphQL and SOAP were not confirmed, and a dedicated bulk or asynchronous API was not confirmed.

Does 15Five provide webhooks or real-time events?

Broad webhook or outbound callback support was not confirmed. Availability, event types, authentication, signatures, retries, and delivery guarantees must be verified with 15Five for the required resources. Martini can use scheduled polling when callbacks are unavailable.

How should 15Five synchronization handle sensitive data and duplicates?

Use stable 15Five or source-system identifiers for idempotent upserts, maintain checkpoints, and separate create, update, deactivation, and deletion rules. Reviews, Check-ins, feedback, and recognition may contain sensitive information, so transfer only approved fields and avoid logging full response bodies.

Can Martini expose an API façade for 15Five?

Yes. Martini can expose a controlled REST API that accepts a normalized employee, objective, or performance payload, applies authentication and validation, and invokes supported 15Five REST operations. This can shield downstream applications from 15Five-specific schemas and credential details.

Related Martini documentation

15Five API

Workflows

Data Processing

Security

Operations

Plan your 15Five integration

Use Martini to connect 15Five with your HR, analytics, identity, and collaboration systems through secure REST API workflows, reusable mappings, controlled business rules, and operationally reliable synchronization.

EXPLORE MARTINI
BOOK A DEMO