Mycashflow Fi MyCashflow API

Name: MyCashflow API
Brand: MyCashflow API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbasic55 EndpointsREST

For Agents

Manage MyCashflow products, orders, customers, categories, banners, brands, payments, shipments, and stock through 55 CRUD operations. Returns store data scoped to the authenticated tenant.

Install Jentic One Beta

Connect the MyCashflow API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyCashflow API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MyCashflow API.

Manage the product catalog including titles, prices, and category links

Browse and update categories and brands that organize products

Read and update orders through their lifecycle including payments and shipments

GET STARTED

Start building with MyCashflow API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MyCashflow API for, with concrete tasks.

★ Catalog Sync from a PIM

Sync a product catalog from an upstream Product Information Management system into MyCashflow on a schedule. The integration pages through GET /products, then issues POST or PATCH calls per product to create or update entries; brands and categories are synced via the parallel /brands and /categories endpoints. With 55 CRUD endpoints, the full storefront data model can be kept in lockstep with the PIM.

For each product changed in the PIM, call PATCH /products/{id} or POST /products, then verify with GET /products/{id} that the update succeeded.

Order Fulfillment Pipeline

Move new MyCashflow orders into a warehouse fulfillment pipeline and write back shipment data. The integration polls GET /orders for new entries, posts shipment records to /shipments as packages leave the warehouse, and updates payment status via /payments. This automates the manual order-handling clicks that small store operators traditionally do in the admin UI.

Poll GET /orders for status=new, then for each order call POST /shipments to record dispatch and PATCH /orders/{id} to mark it as shipped.

Inventory Reconciliation

Reconcile stock levels in MyCashflow against the warehouse system of truth. The integration lists stock entries via GET /stock and issues PATCH calls to bring MyCashflow's quantity into agreement with the warehouse count. This prevents oversells when the warehouse and storefront drift apart.

For each SKU in the warehouse export, call PATCH /stock/{id} with the corrected quantity if it differs from the warehouse count.

Storefront Merchandising Updates

Schedule banner and banner-group updates for promotions without logging into the MyCashflow admin. The /banners and /banner-groups endpoints expose CRUD over the merchandising surface, so a marketing scheduler can swap creative assets and target groups on a calendar. This decouples the marketing calendar from manual store ops.

On the promotion start date, PATCH /banners/{id} to set the new image URL and PATCH /banner-groups/{id} to enable the group.

AI Agent Store Operations Assistant

Wire a Jentic-driven assistant that handles routine store operations on natural-language requests. The agent searches Jentic for 'create a product' or 'list recent orders', loads the matching MyCashflow operation, and executes it. Jentic injects the basic auth credentials at execution time so the agent never holds the store's password.

Through Jentic, search for 'create a MyCashflow product', load POST /products, and create a new product with the title, price, and category provided in the user request.

Key Endpoints

55 endpoints — jentic publishes the only available openapi specification for mycashflow api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

List products

POST

/products

Create a product

GET

/orders

List orders

GET

/customers

List customers

GET

/categories

List categories

GET

/brands

List brands

GET

/stock

List stock entries

GET

/banners

List banners

GET

/products

List products

POST

/products

Create a product

GET

/orders

List orders

GET

/customers

List customers

GET

/categories

List categories

GET

/brands

List brands

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MyCashflow basic auth credentials and the store-specific base URL are stored in the Jentic vault and applied at execution time. Agents never embed a store password in their prompts or logs.

Intent-based discovery

Agents search Jentic with intents like 'create a product' or 'list orders' and Jentic returns the matching MyCashflow operation with its input schema, so the agent can act without browsing MyCashflow's developer docs.

Time to first call

Direct integration including basic auth setup, store-name URL templating, and pagination across 55 endpoints typically takes 2-3 days. Through Jentic the search, load, execute flow runs in under an hour.

FAQs

Specific to using MyCashflow API through Jentic.

Why is there no official OpenAPI spec for MyCashflow API?

MyCashflow does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MyCashflow API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MyCashflow API use?

MyCashflow uses HTTP basic authentication with a store-specific username and password issued from the MyCashflow admin. The base URL embeds the store name (https://{storeName}.mycashflow.fi/api/v1). Through Jentic, basic auth credentials are stored in the vault and applied at execution time.

Can I create products via the MyCashflow API?

Yes. POST /products creates a new product, PATCH /products/{id} updates one, and DELETE /products/{id} removes it. The same pattern is exposed for brands, categories, customers, orders, payments, shipments, banners, and stock.

How do I list new orders through Jentic?

Through Jentic, search for 'list MyCashflow orders', load GET /orders, and call it with the desired filter parameters. Jentic forwards the basic auth header from its vault and returns the order list to your agent.

What are the rate limits for the MyCashflow API?

Rate limits are enforced at the gateway and not declared in the OpenAPI spec. Stagger bulk syncs and respect 429 responses; for catalog updates, batch by category or brand to avoid hammering the storefront database.

Can I adjust stock via the MyCashflow API?

Yes. The /stock endpoints expose CRUD over stock entries, so an agent or scheduled job can keep MyCashflow stock counts in sync with a warehouse system using PATCH /stock/{id}.

Mycashflow Fi MyCashflow API

Connect the MyCashflow API to your agent

Capabilities

Start building with MyCashflow API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs