Leapsome

Leapsome auth API

The auth API from Leapsome — 1 operation(s) for auth.

Documentation GitHub OpenAPI

Operations 1

GET /token Get JWT access token #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/leapsome-auth-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  version: 1.0.1
  title: Leapsome absences Auth API
  contact:
    name: Support
    url: https://leapsome.zendesk.com
  description: The Content API enables you to export some raw data from Leapsome for usage within your own systems and beyond what the Leapsome application offers natively. Usage is restricted to a maximum of 20 requests per second when making requests in parallel. If you exceed this limit, you will receive a 429 status code.
servers:
- url: https://api.leapsome.com/v1
tags:
- name: auth
paths:
  /token:
    get:
      summary: Get JWT access token
      operationId: getToken
      security: []
      tags:
      - auth
      parameters:
      - name: secret
        in: query
        required: true
        description: 'API Secret from [Leapsome admin page](www.leapsome.com:3000/app/#/team/settings/)

          '
        schema:
          type: string
        example: yvpBwdF1kE74e2aXuzsG
      responses:
        '200':
          description: Authorization successfull
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AuthInfo'
        '401':
          description: Authorization failed. This usually means that `secret` is missing or is incorrect.
components:
  schemas:
    AuthInfo:
      type: object
      required:
      - token
      - expiresIn
      properties:
        token:
          type: string
          example: <JWT TOKEN>
        expiresIn:
          type: integer
          description: seconds until the token expires
          example: 18000
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT