Docs / Usage and billing

What counts as an API call

An API call is each request Ladeworks makes to one of your integrations. Your plan includes a number of calls each month, and the Workflows page and Plan and billing show how many you have used.

What counts

• Each page of results pulled. A pull that needs 13 pages is 13 calls.
• Each row pushed, or each batch when batching is on.
• Each details request. Get details for each row makes one request per row.
• Each request of Request a report and wait: the one that starts the report, each check on it, and the optional request after it. A report that is ready at the first check costs 2 calls. On Pro and Business.
• Each file downloaded from a link by Read a file from a link: 1 call per file, on top of the request that returned the link. On Pro and Business.
• Each file read or written. Every CSV read and every CSV write is 1 call per file, whether the file is on a file server, an uploaded CSV, or "A CSV to download" that Ladeworks keeps for you.
• Each message sent by a Send a message step (Slack, Discord or email). Alert emails and chat messages that Ladeworks sends on its own are not calls.

Test runs ("Test with 10 rows") count like any other run.

What is free

• Filtering, mapping, removing duplicates, waiting and "End run if" checks.
• Retries. Only the first attempt counts.
• Folder checks for "When a file lands" that find no new file. On Pro and Business.
• Runs rejected before any file is read or request is made, for example a file over the size limit.
• A write that produces no file, when there are no rows and "write an empty file" is off.
• Records you already sent, when the Push option "Don't send records that were already sent" is on (see Cutting calls).

Where you see them

The builder shows an estimate for each workflow: "About 113 API calls per run" and, for scheduled workflows, "a month at this schedule". The estimate uses your last 5 successful runs. A workflow that has never run is estimated on 100 rows, and filters are assumed to keep every row, so the number is an upper bound. Each run's details show the calls it used. The Workflows page shows each workflow's calls this month and its share of the total. See Usage and the spending cap.