Aiviue
QSR & HospitalityLogistics & DeliveryAutomotiveBFSIRetail
JobsJob SeekersInsightsAboutHire Now

Get started

  • Overview
  • Quickstart

Guides

  • Authentication
  • Tenants
  • Idempotency
  • Webhooks
  • Errors and rate limits
  • Sandbox
  • Versioning and changelog

Reference

  • API reference

Guide

Tenants

How your customers map to Aiviue tenants and the X-Tenant-ID header.

View as markdown

A tenant is one of your customers — the employer you are hiring for. Each tenant has its own jobs, candidates and usage inside Aiviue, and one partner account can manage several tenants.

The X-Tenant-ID header

Send the tenant on every resource request:

X-Tenant-ID: <tenant id>

The value is the Aiviue tenant ID we give you when a tenant is set up — not an ID from your own system. Store the mapping between your customer and its Aiviue tenant ID on your side.

Requests that don't need a tenant:

  • POST /v1/auth/token, POST /v1/auth/token/revoke, GET /v1/auth/.well-known/jwks.json
  • GET /v1/integration/health and GET /v1/integration/health/detailed

Errors

SituationStatuserror.code
Header missing400VALIDATION_ERROR (with field: "X-Tenant-ID")
Tenant ID not found404NOT_FOUND
Tenant belongs to a different partner403FORBIDDEN

Your own IDs

Your IDs live in the request bodies, not in headers. For example external_job_id on a job is your stable job ID, and external_client_id can carry your own customer reference.

NextIdempotency →

Aiviue

AI hiring software for frontline teams in India

Company

  • About Us
  • Pricing
  • Insights
  • Job Seekers
  • Developers
  • Hire Now

Industries

  • QSR & Hospitality
  • Logistics & Delivery
  • Automotive
  • BFSI
  • Retail

© 2026 Aiviue. All rights reserved.

Privacy PolicyTerms of ServiceRefund PolicyCancellation Policy