Data Dictionary

This page lists every field, enum, and taxonomy used across the Himalayas JSON API, RSS feed, and MCP server. Use it as a reference when building integrations, configuring AI agents, or validating data from any Himalayas endpoint.

What fields does the Himalayas API return for each job?

Every job returned by the JSON API, RSS feed, and MCP server includes the following fields:

For field-level documentation in machine-readable format, see the OpenAPI specification.

What are the valid employment types?

The employmentType field uses one of these exact string values:

What are the valid seniority levels?

The seniority field is an array containing one or more of these exact string values:

A single job can target multiple seniority levels - for example, ["Mid-level", "Senior"] for a role open to either.

What currencies does Himalayas support?

The currency field uses ISO 4217 three-letter currency codes. Himalayas supports 29 currencies:

Salary values (minSalary, maxSalary) are annual amounts in the specified currency. If no salary is provided, the salary fields are null and the currency field may still indicate the company's preferred currency.

What is the format of location restrictions?

The locationRestrictions field is an array of location objects. Each object has three properties:

{
  "alpha2": "US",
  "name": "United States",
  "slug": "united-states"
}

An empty locationRestrictions array means the job has no location restrictions and is open worldwide.

What is the format of timezone restrictions?

The timezoneRestrictions field is an array of UTC offset strings:

["UTC-8", "UTC-7", "UTC-6", "UTC-5"]

Offsets can include half-hour increments (e.g., "UTC+5:30" for India Standard Time). An empty array means the job has no timezone restrictions.

What company size ranges does Himalayas use?

Company profiles on Himalayas include an employee range field with one of these values:

Company size appears on company profiles and in the talent directory. It is not returned in the Jobs API response.

What education credential categories exist?

Jobs that specify education requirements use these credential categories:

A job's educationRequirementStatus can be "required", "none", or "unknown". When set to "required", the educationCredentialCategories array lists acceptable credential levels.

What screening question types are available?

Employers can add screening questions to job applications. Each question has a type that determines the answer format:

What benefit categories does Himalayas track?

Company profiles can include benefits from 30 predefined categories:

Benefits appear on company profiles and are searchable in the talent directory and company directory.

Are job categories and skills fixed or dynamic?

Job categories, parent categories, skills, technologies, and markets are dynamic: they are managed on the backend and change as new jobs are posted and new companies are added. The API returns them as string arrays.

The following fields are fixed enums that do not change:

• employmentType - 7 values for job listings, 10 values for profile experience (see above)
• seniority - 6 values (see above)
• currency - 29 values (see above)
• educationCredentialCategories - 5 values (see above)
• screeningQuestionType - 3 values: boolean, text, mpc
• careerSearchStatus - 3 values: actively_searching, open_to_roles, closed_to_roles
• kanbanStatus - 7 values: seen, saved, applied, interviewing, negotiation, hired, archived
• benefitCategory - 30 values (see above)
• jobPostingExtra - 2 values: sticky, newsletter

What are the job application tracker statuses?

The Himalayas Job Application Tracker uses a kanban-style board with these statuses:

What career search statuses does Himalayas use?

Talent profiles include a career search status that indicates availability. This field is used in the MCP server update_profile tool and on public talent profiles.

What employment types are available for profile experience?

When adding work experience to a talent profile via the MCP server, an extended set of 10 employment types is available. This is a superset of the 7 job listing employment types.

How do search filters differ from data field values in the MCP server?

The MCP server search_jobs tool uses lowercase, hyphenated values for its experience and type filter parameters. These are different from the capitalized values stored in job data fields and used in job creation tools.

The JSON API and RSS feed return the capitalized data field values (e.g., "Full Time", "Entry-level").

What sort options are available in the MCP server?

The MCP server search tools accept a sort parameter. Available options vary by tool.

Job search (search_jobs):

Company search (search_companies):

Talent search (search_talent):

What statistics dimensions does the MCP server support?

The MCP server get_remote_work_statistics tool accepts two parameters that control what data is returned.

Record type (record):

Breakdown dimension (type):

What paid extras are available for job postings?

When posting jobs through the MCP server create_company_job or purchase_job_extras tools, employers can add paid extras:

Extras can be added at job creation or purchased later for an existing job.

Where can I get help?

For questions about data formats or field values, email hi@himalayas.app.

For integration guides, see the AI Agents hub, JSON API, RSS Feed, or MCP Server documentation.