DATPAQ Working Days API

Business day calculations with regional holiday support

Operations 3

POST /working-days/calculate Calculate working days between dates or offset business days #
GET /working-days/calculate Calculate working days (GET) #
GET /working-days/calculate/batch Batch working day calculations #

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/datpaq-com:datpaq-com-working-days-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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

OpenAPI Specification

datpaq-com-working-days-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Datpaq Com Working Days API
  version: 1.1.0
  contact:
    name: Datpaq Support
    url: https://datpaq.com
  license:
    name: Proprietary
  description: 'Operations tagged Working Days across 2 of this provider''s published API definitions: datpaq-com.yaml, datpaq-com-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://datpaq.com/api/v1
  description: Production
- url: https://staging.datpaq.com/api/v1
  description: Staging
security:
- ApiKeyHeader: []
- ApiKeyQuery: []
tags:
- name: Working Days
  description: Business day calculations with regional holiday support
paths:
  /working-days/calculate:
    post:
      tags:
      - Working Days
      operationId: workingDaysCalculatePost
      summary: Calculate working days between dates or offset business days
      description: 'For range calculations: provide start_date and end_date to get the number of working days between them. For offset calculations: provide start_date and days_offset to find the resulting business date. Supports US, DE, and IN regional holiday calendars.'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - start_date
              properties:
                start_date:
                  type: string
                  format: date
                  example: '2026-01-01'
                end_date:
                  type: string
                  format: date
                  example: '2026-01-31'
                days_offset:
                  type: integer
                  description: Working days to add (positive) or subtract (negative)
                  example: 10
                direction:
                  type: string
                  enum:
                  - forward
                  - backward
                  default: forward
                region:
                  type: string
                  description: Regional holiday calendar
                  enum:
                  - US
                  - DE
                  - IN
                  default: US
            example:
              start_date: '2026-07-01'
              end_date: '2026-07-15'
              region: US
      responses:
        '200':
          description: Working day calculation result
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenericSuccess'
              example:
                working_days: 7
                start_date: '2025-07-01'
                end_date: '2025-07-10'
                region: US
                holidays_used:
                - '2025-07-04'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '429':
          $ref: '#/components/responses/RateLimited'
        default:
          $ref: '#/components/responses/ServiceUnavailable'
    get:
      tags:
      - Working Days
      operationId: workingDaysCalculateGet
      summary: Calculate working days (GET)
      parameters:
      - name: start_date
        in: query
        required: true
        schema:
          type: string
          format: date
          example: '2026-01-01'
      - name: end_date
        in: query
        required: false
        schema:
          type: string
          format: date
      - name: days_offset
        in: query
        required: false
        schema:
          type: integer
      - name: region
        in: query
        required: false
        schema:
          type: string
          enum:
          - US
          - DE
          - IN
          default: US
      responses:
        '200':
          description: Working day calculation result
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenericSuccess'
              example:
                working_days: 7
                start_date: '2025-07-01'
                end_date: '2025-07-10'
                region: US
                holidays_used:
                - '2025-07-04'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '429':
          $ref: '#/components/responses/RateLimited'
        default:
          $ref: '#/components/responses/ServiceUnavailable'
    servers:
    - url: https://datpaq.com/api/v1
      description: Production
    - url: https://staging.datpaq.com/api/v1
      description: Staging
  /working-days/calculate/batch:
    get:
      tags:
      - Working Days
      operationId: workingDaysBatch
      summary: Batch working day calculations
      parameters:
      - name: requests
        in: query
        required: true
        description: JSON-encoded array of calculation requests
        schema:
          type: string
          example: '[{"start_date":"2026-01-01","end_date":"2026-01-31"}]'
      responses:
        '200':
          description: Batch calculation results
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenericSuccess'
              example:
              - working_days: 7
                start_date: '2025-07-01'
                end_date: '2025-07-10'
                region: US
              - working_days: 5
                start_date: '2025-08-01'
                end_date: '2025-08-08'
                region: US
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '429':
          $ref: '#/components/responses/RateLimited'
        default:
          $ref: '#/components/responses/ServiceUnavailable'
    servers:
    - url: https://datpaq.com/api/v1
      description: Production
    - url: https://staging.datpaq.com/api/v1
      description: Staging
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message
          example: Invalid API key
        correlationId:
          type: string
          description: Request tracking identifier for support
          example: abc123-def456-789ghi
        service:
          type: string
          description: Service name that produced the error
          example: ip-geolocation
    GenericSuccess:
      type: object
      description: Standard success envelope. The data property structure varies by endpoint.
      properties:
        correlationId:
          type: string
          description: Request tracking identifier
          example: abc123-def456
        data:
          type: object
          description: Response payload (structure varies by endpoint)
        cached:
          type: boolean
          description: Whether the response was served from cache
          example: false
  responses:
    BadRequest:
      description: Bad request — missing or invalid parameters
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    RateLimited:
      description: Rate limit exceeded — retry after the indicated period
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    ServiceUnavailable:
      description: Service temporarily unavailable
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    Unauthorized:
      description: Unauthorized — missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    ApiKeyHeader:
      type: apiKey
      in: header
      name: x-api-key
      description: API key passed via x-api-key request header
    ApiKeyQuery:
      type: apiKey
      in: query
      name: api_key
      description: API key passed as api_key query parameter
x-refined-from:
- datpaq-com.yaml
- datpaq-com-openapi.yaml