Skip to content
ESEN

Cord Developers

Integrate Cord with your systems: REST API, webhooks, Node SDK, CLI, MCP server and Cord Elements.

Cord’s API is resource-oriented, responds with JSON and standard HTTP status codes, and is available on every plan. Every response carries a Cord-Request-Id, every write accepts Idempotency-Key, and every key is pinned to an API version. Start with the Quickstart: in five minutes you create a quote and receive its webhook on your machine.

What you can build

  • Sync your ERP or CRM: keep your catalog and clients up to date with the Products API and the Clients API.
  • React to events: mark an order as paid when quote.paid arrives by webhook, or reconcile with the event history.
  • Invoice from your system: create, issue and collect invoices with the Invoices API.
  • Connect AI agents: give Claude or ChatGPT access to your data with the MCP server, or let them propose an account’s setup with assisted setup.
  • Embed the close in your product: quote, invoice and tax form with Cord Elements.
  • Ship an app for many businesses: connect it with OAuth instead of asking for keys.

SDKs and tools

Tool Install What for
v1 REST API — https://cordhq.app/api/v1, with any HTTP client.
Node SDK npm install @flouviahq/node The full API from your server, with retries, idempotency and webhook verification. Node, Bun, Deno and edge.
Cord Elements npm install @flouviahq/elements Quote, invoice and tax form in the browser: React, Vue, Web Components and headless.
CLI npx @flouviahq/cli Browser sign-in, AI setup, project integration and webhooks on your localhost.
MCP server — Tools for AI agents over your data.
Cord Workbench — Keys, endpoints, events and the log of every request, inside the app.
Python and PHP — Not published yet. Use the REST API directly.

Specification and machine-readable resources

Resource Address
OpenAPI 3.1 (JSON) https://cordhq.app/openapi.json
OpenAPI 3.1 (YAML) https://cordhq.app/openapi.yaml
Summary for AI assistants https://cordhq.app/llms.txt
All the documentation in one file https://cordhq.app/llms-full.txt
Browsable reference API Reference

Test environments

Every account has an isolated test environment: what you create with an sk_test_ key or with the app’s test mode doesn’t touch your real data. With a test key you get simulators to trigger stamping, expirations and webhooks, and cord listen to receive them on your machine. The exception is assisted setup proposals, which always go to your real account and are only applied if a person approves them. See Test environments.

The Workbench in the test environment, on the Logs tab: the quickstart requests made with cURL and the test key, one with the invalid_request error and one from the Workbench Shell, and the detail of POST /v1/cotizaciones (201, 184 ms) with its request id, version 2026-10-01, Test mode and the Copy as cURL and Open in Shell buttons.

All pages

Get started

Tools

Cord Elements

Essentials

Features

Security & Privacy