/ Docs
Vendor Integrations

15five

Last updated October 13, 2025 · View as Markdown

15Five_logo.png 15five is an HR performance management platform. Through a lightweight weekly check-in, 15Five helps managers measure and drive employee engagement and performance, including continuous feedback, objective (OKR) tracking, peer recognition, 1-on-1s, and reviews.

In order to integrate 15five with Relyance AI you will need to generate an API key.

In 15five:

  1. Login to your 15five account.
  2. Click on your Settings menu at the top right and then click Features.
  3. Scroll to the bottom of the page and click on Integrations.
  4. Scroll down to the Public API entry and click the Enable button on its right.
  5. You will be taken to the Company API Keys page.
  6. Click the Create new key button.
  7. Add in a short name for your API key. This name can be anything; usually, this is a name that is easily identifiable from your server-side.
  8. Ensure the Enabled box is ticked, and click Save.
  9. You will be redirected back to the Company API keys page to verify your API key and access token. Record this token temporarily for use in the later Relyance AI integration steps.
  10. The subdomain endpoint for your API, assuming you do not have a unique subdomain, is my (from my.15five.com).

mceclip0.png

mceclip1.png

mceclip2.png

mceclip3.png

mceclip4.png

In Relyance AI:

  1. Login to your Relyance account.
  2. Navigate to the Settings Menu in the bottom left-hand side.
  3. Select Integrations.
  4. Click on the Vendors and Data Stores filter.
  5. Find the 15five integration card and click it to open its connections.
  6. Under Authentication Method, choose Custom.
  7. Paste the Subdomain and API access token from the previous 15five configuration steps into their respective fields.

mceclip6.png

The Authentication step asks for:

  • Subdomain: required.
  • API Key: required; held as a secret.
  1. Click Authenticate.
  2. At this point, you should see the following result on the Vendor Integrations page:

mceclip7.png

  1. Congratulations, you are now integrated with 15five.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

  1. A credential rotated at the vendor is not picked up here. API Key is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
  2. Check the address fields before suspecting the credentials. Subdomain identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "15five" {
  vendor = "15five"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      subdomain = "my"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_key = var.15five_api_key
    }
    secrets_wo_version = 1
  }

  scans = { "property-inspection" = { enabled = true } }
}