Skip to content

midday-ai/midday-ts

BranchesTags

Repository files navigation

Midday TypeScript SDK to interact with APIs.

Midday TypeScript SDK


Learn more about the Midday TypeScript SDK in the official documentation.

Summary

Midday API: Midday is a platform for Invoicing, Time tracking, File reconciliation, Storage & Financial Overview.

Table of Contents

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add @midday-ai/sdk

PNPM

pnpm add @midday-ai/sdk

Bun

bun add @midday-ai/sdk

Yarn

yarn add @midday-ai/sdk zod

# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.

Note

This package is published with CommonJS and ES Modules (ESM) support.

Model Context Protocol (MCP) Server

This SDK is also an installable MCP server where the various SDK methods are exposed as tools that can be invoked by AI applications.

Node.js v20 or greater is required to run the MCP server from npm.

Claude installation steps

Add the following server definition to your claude_desktop_config.json file:

{
  "mcpServers": {
    "Midday": {
      "command": "npx",
      "args": [
        "-y", "--package", "@midday-ai/sdk",
        "--",
        "mcp", "start",
        "--oauth2", "...",
        "--api-token", "..."
      ]
    }
  }
}
Cursor installation steps

Create a .cursor/mcp.json file in your project root with the following content:

{
  "mcpServers": {
    "Midday": {
      "command": "npx",
      "args": [
        "-y", "--package", "@midday-ai/sdk",
        "--",
        "mcp", "start",
        "--oauth2", "...",
        "--api-token", "..."
      ]
    }
  }
}

You can also run MCP servers as a standalone binary with no additional dependencies. You must pull these binaries from available Github releases:

curl -L -o mcp-server \
    https://github.com/{org}/{repo}/releases/download/{tag}/mcp-server-bun-darwin-arm64 && \
chmod +x mcp-server

If the repo is a private repo you must add your Github PAT to download a release -H "Authorization: Bearer {GITHUB_PAT}".

{
  "mcpServers": {
    "Todos": {
      "command": "./DOWNLOAD/PATH/mcp-server",
      "args": [
        "start"
      ]
    }
  }
}

For a full list of server arguments, run:

npx -y --package @midday-ai/sdk -- mcp start --help

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

import { Midday } from "@midday-ai/sdk";

const midday = new Midday({
  security: {
    oauth2: process.env["MIDDAY_OAUTH2"] ?? "",
  },
});

async function run() {
  const result = await midday.oAuth.postOAuthRegister({
    clientName: "ChatGPT",
    redirectUris: [
      "https://chatgpt.com/connector/oauth/callback",
    ],
    grantTypes: [
      "authorization_code",
      "refresh_token",
    ],
    scope: "transactions.read invoices.read",
    logoUri: "https://example.com/logo.png",
    clientUri: "https://example.com",
    responseTypes: [
      "code",
    ],
  });

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security schemes globally:

Name Type Scheme Environment Variable
oauth2 oauth2 OAuth2 token MIDDAY_OAUTH2
token http HTTP Bearer MIDDAY_TOKEN

You can set the security parameters through the security optional parameter when initializing the SDK client instance. The selected scheme will be used by default to authenticate with the API for all operations that support it. For example:

import { Midday } from "@midday-ai/sdk";

const midday = new Midday({
  security: {
    oauth2: process.env["MIDDAY_OAUTH2"] ?? "",
  },
});

async function run() {
  const result = await midday.oAuth.postOAuthRegister({
    clientName: "ChatGPT",
    redirectUris: [
      "https://chatgpt.com/connector/oauth/callback",
    ],
    grantTypes: [
      "authorization_code",
      "refresh_token",
    ],
    scope: "transactions.read invoices.read",
    logoUri: "https://example.com/logo.png",
    clientUri: "https://example.com",
    responseTypes: [
      "code",
    ],
  });

  console.log(result);
}

run();

Available Resources and Operations

Available methods

bankAccounts

  • list - List all bank accounts
  • create - Create a bank account
  • get - Retrieve a bank account
  • update - Update a bank account
  • delete - Delete a bank account

customers

  • list - List all customers
  • create - Create customer
  • get - Retrieve a customer
  • update - Update a customer
  • delete - Delete a customer

desktop

documents

files

inbox

  • list - List all inbox items
  • get - Retrieve a inbox item
  • delete - Delete a inbox item
  • update - Update a inbox item
  • getPreSignedUrl - Generate pre-signed URL for inbox attachment

integrations

invoicePayments

invoices

notifications

oAuth

reports

search

tags

teams

  • list - List all teams
  • get - Retrieve a team
  • update - Update a team
  • members - List all team members

trackerEntries

  • list - List all tracker entries
  • create - Create a tracker entry
  • createBulk - Create multiple tracker entries
  • update - Update a tracker entry
  • delete - Delete a tracker entry

trackerProjects

  • list - List all tracker projects
  • create - Create a tracker project
  • update - Update a tracker project
  • get - Retrieve a tracker project
  • delete - Delete a tracker project

trackerTimer

transactions

users

  • get - Retrieve the current user
  • update - Update the current user

webhooks

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

Available standalone functions

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

import { Midday } from "@midday-ai/sdk";

const midday = new Midday({
  security: {
    oauth2: process.env["MIDDAY_OAUTH2"] ?? "",
  },
});

async function run() {
  const result = await midday.oAuth.postOAuthRegister({
    clientName: "ChatGPT",
    redirectUris: [
      "https://chatgpt.com/connector/oauth/callback",
    ],
    grantTypes: [
      "authorization_code",
      "refresh_token",
    ],
    scope: "transactions.read invoices.read",
    logoUri: "https://example.com/logo.png",
    clientUri: "https://example.com",
    responseTypes: [
      "code",
    ],
  }, {
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  console.log(result);
}

run();

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

import { Midday } from "@midday-ai/sdk";

const midday = new Midday({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  security: {
    oauth2: process.env["MIDDAY_OAUTH2"] ?? "",
  },
});

async function run() {
  const result = await midday.oAuth.postOAuthRegister({
    clientName: "ChatGPT",
    redirectUris: [
      "https://chatgpt.com/connector/oauth/callback",
    ],
    grantTypes: [
      "authorization_code",
      "refresh_token",
    ],
    scope: "transactions.read invoices.read",
    logoUri: "https://example.com/logo.png",
    clientUri: "https://example.com",
    responseTypes: [
      "code",
    ],
  });

  console.log(result);
}

run();

Error Handling

MiddayError is the base class for all HTTP error responses. It has the following properties:

Property Type Description
error.message string Error message
error.statusCode number HTTP response status code eg 404
error.headers Headers HTTP response headers
error.body string HTTP body. Can be empty string if no body is returned.
error.rawResponse Response Raw HTTP response
error.data$ Optional. Some errors may contain structured data. See Error Classes.

Example

import { Midday } from "@midday-ai/sdk";
import * as errors from "@midday-ai/sdk/models/errors";

const midday = new Midday({
  security: {
    oauth2: process.env["MIDDAY_OAUTH2"] ?? "",
  },
});

async function run() {
  try {
    const result = await midday.oAuth.postOAuthRegister({
      clientName: "ChatGPT",
      redirectUris: [
        "https://chatgpt.com/connector/oauth/callback",
      ],
      grantTypes: [
        "authorization_code",
        "refresh_token",
      ],
      scope: "transactions.read invoices.read",
      logoUri: "https://example.com/logo.png",
      clientUri: "https://example.com",
      responseTypes: [
        "code",
      ],
    });

    console.log(result);
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.MiddayError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);

      // Depending on the method different errors may be thrown
      if (error instanceof errors.OAuthErrorResponse) {
        console.log(error.data$.error); // string
        console.log(error.data$.errorDescription); // string
        console.log(error.data$.errorUri); // string
        console.log(error.data$.state); // string
      }
    }
  }
}

run();

Error Classes

Primary error:

  • MiddayError: The base class for HTTP error responses.
Less common errors (44)

Network errors:

Inherit from MiddayError:

* Check the method documentation to see if the error is applicable.

Server Selection

Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:

import { Midday } from "@midday-ai/sdk";

const midday = new Midday({
  serverURL: "https://api.midday.ai",
  security: {
    oauth2: process.env["MIDDAY_OAUTH2"] ?? "",
  },
});

async function run() {
  const result = await midday.oAuth.postOAuthRegister({
    clientName: "ChatGPT",
    redirectUris: [
      "https://chatgpt.com/connector/oauth/callback",
    ],
    grantTypes: [
      "authorization_code",
      "refresh_token",
    ],
    scope: "transactions.read invoices.read",
    logoUri: "https://example.com/logo.png",
    clientUri: "https://example.com",
    responseTypes: [
      "code",
    ],
  });

  console.log(result);
}

run();

Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native Fetch API. This client is a thin wrapper around fetch and provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient constructor takes an optional fetcher argument that can be used to integrate a third-party HTTP client or when writing tests to mock out the HTTP client and feed in fixtures.

The following example shows how to use the "beforeRequest" hook to to add a custom header and a timeout to requests and how to use the "requestError" hook to log errors:

import { Midday } from "@midday-ai/sdk";
import { HTTPClient } from "@midday-ai/sdk/lib/http";

const httpClient = new HTTPClient({
  // fetcher takes a function that has the same signature as native `fetch`.
  fetcher: (request) => {
    return fetch(request);
  }
});

httpClient.addHook("beforeRequest", (request) => {
  const nextRequest = new Request(request, {
    signal: request.signal || AbortSignal.timeout(5000)
  });

  nextRequest.headers.set("x-custom-header", "custom value");

  return nextRequest;
});

httpClient.addHook("requestError", (error, request) => {
  console.group("Request Error");
  console.log("Reason:", `${error}`);
  console.log("Endpoint:", `${request.method} ${request.url}`);
  console.groupEnd();
});

const sdk = new Midday({ httpClient: httpClient });

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass a logger that matches console's interface as an SDK option.

Warning

Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.

import { Midday } from "@midday-ai/sdk";

const sdk = new Midday({ debugLogger: console });

You can also enable a default debug logger by setting an environment variable MIDDAY_DEBUG to true.

About

Official Midday Typescript SDK

Resources

Readme

Contributing

Contributing
Activity
Custom properties

Stars

7 stars

Watchers

0 watching

Forks

3 forks
Report repository

Releases 14

typescript - v0.6.0 - 2026-03-27 14:07:56 Latest
Mar 27, 2026
+ 13 releases

Packages

 
 
 

Contributors

Languages