Tip Calculator API

About the Tip Calculator API

Tip Calculator takes a pre-tip bill, a tip percentage and the number of people at the table, and returns the tip, the total and each person's share of the bill, the tip and the total. Works as a tip calculator and bill splitter in one call, with common tip percentages included for comparison. It handles a 0% tip correctly and defaults to 15% and one person when those values are left out.

Restaurant and dining apps use it at checkout, expense and group-payment tools use it to split bill totals fairly, and point-of-sale screens use it to suggest a gratuity before the customer chooses one.

The Free plan returns the bill, tip percentage, tip amount, total, currency code and the per-person breakdown. Paid plans add a comparison table at 10, 15, 18, 20 and 25 percent with the tip, total and per-person figure for each, and display-ready strings with the currency symbol already attached, so a gratuity calculator screen can render without its own formatting code.

How it works

The tip is amount multiplied by percentage / 100, and the total is the bill plus the tip. percentage accepts 0 to 100 and defaults to 15; a 0 is honoured rather than replaced by the default. people defaults to 1, and the bill, tip and total are each divided by it to give the per_person object.

Every money figure is rounded to two decimal places independently, after the division. Because the per-person values are rounded from unrounded totals, multiplying per_person.total_amount back by split_between can differ from total_amount by a cent or so; if you collect money from each person, decide in your own code who covers the remainder.

currency is a display setting only and no exchange conversion takes place. It is echoed back as sent, and it chooses the symbol used in formatted: USD, EUR, GBP, JPY, CNY, INR, CAD, AUD and MXN have built-in symbols (CAD shows C$, AUD A$, MXN MX$), and any other code is printed as the code followed by a space. The match is case-sensitive, and all currencies are formatted with two decimals, including JPY.

common_tip_amounts repeats the calculation for 10, 15, 18, 20 and 25 percent, each with tip_amount, total and per_person, regardless of the percentage you asked for. formatted and common_tip_amounts are null on the Free plan; all other fields are returned on every plan.

What people use it for

Dining Apps

Integrate tip calculation features into restaurant and food delivery applications

Expense Tracking

Calculate and track tip expenses for budgeting and expense reporting

Bill Splitting

Split restaurant bills fairly among groups with automatic tip calculation

Financial Tools

Provide tip guidance and calculation in personal finance and budgeting apps

Without writing code

The Tip Calculator widget from WidgetSpark splits the bill from your desktop.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/tipcalculator

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Optional

1
2

curl "https://api.apiverve.com/v1/tipcalculator?amount=100&percentage=18&people=4&currency=USD" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/tipcalculator

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

{
  "status": "ok",
  "error": null,
  "data": {
    "bill_amount": 100,
    "tip_percentage": 18,
    "tip_amount": 18,
    "total_amount": 118,
    "currency": "USD",
    "split_between": 4,
    "per_person": {
      "bill_amount": 25,
      "tip_amount": 4.5,
      "total_amount": 29.5
    },
    "common_tip_amounts": [
      {
        "percentage": 10,
        "tip_amount": 10,
        "total": 110,
        "per_person": 27.5
      },
      {
        "percentage": 15,
        "tip_amount": 15,
        "total": 115,
        "per_person": 28.75
      },
      {
        "percentage": 20,
        "tip_amount": 20,
        "total": 120,
        "per_person": 30
      }
    ],
    "formatted": {
      "bill_amount": "$100.00",
      "tip_amount": "$18.00",
      "total_amount": "$118.00",
      "per_person_total": "$29.50"
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 1 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Tip Calculator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Tip Calculator API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1