Billing and credits

A paying developer manages money for a subscription in your API Portal. Paid plans show a Billing tab with invoices and a link to the Stripe customer portal, usage plans show consumption, and prepaid plans top up a credit balance on the team. Request logs are a separate, optional view. What a developer sees depends on the plan and on their billing access.

Where does a developer see billing for a subscription?

On a paid subscription, the subscription has a Billing tab. It shows the billing cycle, the next invoice date, the pricing details, consumption where the plan meters usage, and an invoice history. Open Stripe Customer Portal takes the developer to Stripe to manage payment details.

When is the Billing tab hidden?

The Billing tab appears only when the subscription bills through Stripe and the member can read billing. It is hidden in these cases:

• The plan is free, contract, or prepaid. Prepaid plans use the team's Credits tab instead.
• The subscription is Pending Approval.
• The member has no billing access in the team. Read Only or Full billing access shows the tab.
• Your team activated the subscription from the dashboard, which bypasses payment, so there is no Stripe subscription.

How does a developer pay, or recover from a failed payment?

From the subscription page. A subscription in Pending Payment shows a Checkout button that opens Stripe checkout. A subscription in Payment Failed shows View and pay open invoice, which opens the unpaid invoice.

A subscription reaches Pending Payment when the developer subscribes to a paid plan, when your team approves a paid subscription, or when your team approves a paid sandbox subscription for production. Once a checkout has been started, a Refresh status icon next to the status re-reads the status from Stripe.

What does consumption show?

On usage-based and overage plans, the Billing tab shows how much has been used in the current billing period, as reported to Stripe. Free and flat-fee plans show no consumption, because nothing is metered.

Consumption follows the same Stripe condition as the Billing tab. On AWS, usage reaches Apiable through your gateway's usage logs; see Enable usage logs on AWS API Gateway. See Anatomy of a plan for how a plan's revenue model sets which view applies.

How does a developer top up prepaid credits?

On a prepaid plan, the team carries a credit balance instead of recurring invoices. The team's Credits tab shows the balance and lets a developer add to it by creating an invoice. The team draws the balance down as it calls your paid APIs.

1. The developer opens their team and goes to the Credits tab. It appears once the team has a subscription on a prepaid plan.
2. They see the credit left per currency and the list of credit lines.
3. They pick a Currency and an Amount, then click Create Invoice for {amount} {currency}. The minimum amount is 10.
4. The invoice opens in a new tab. Once it is paid, the credit becomes active.

Each credit line shows its amount, type, invoice number, created date, status, and expiry. A credit is Active, Pending, or Void. Spent and voided lines are hidden unless the developer turns on Show spent and voided credits. The currency is fixed once the team has an active credit. Creating a top-up needs Full billing access in the team.

An active prepaid subscription also shows a Prepaid credits block with the team's balance and a Manage credits link.

Can a developer see request logs?

When usage reporting is enabled for your portal, each subscription has a Logs tab. It lists recent requests, so a developer can confirm their calls are landing and check status codes. The Logs tab is separate from billing and does not depend on the plan being paid.

Above the table, two charts show API Calls by Status Code and API Calls Over Time. The table is sortable and shows one row per request:

On AWS plans with a rate limit, an active subscription also shows its API usage against the limit on the Details tab.

Where to next