Gamma API Pricing and Credit Costs for Bulk Deck Generation

Gamma's API is billed in credits, not per call, and the number that decides your invoice is not how many decks you generate. It is which image model you pass. Text-led slides cost 1 to 3 credits per card, roughly half a cent, so even a few hundred decks a month is small money. Switch imageOptions.model to a premium or ultra tier and the same volume costs two to three orders of magnitude more. Gamma publishes both numbers; almost nobody puts them next to each other.

Last updated September 2026. Figures here come from Gamma's own developer documentation at developers.gamma.app, specifically "Review access and pricing" and the export endpoint reference, and from the Gamma help center articles "How do credits work in Gamma?" and "How do I purchase more credits?" (dated 23 July 2026). Gamma's public pricing page blocks automated retrieval, so seat prices are not quoted here as precise figures. Credit figures are first-party and exact.

Which Gamma plans can use the API at all

Start here, because it disqualifies the two cheapest tiers outright. Gamma's developer docs state that "API keys are available on Pro, Ultra, Teams, and Business plans". Free and Plus cannot generate an API key, so if you are on Plus and planning an integration, the integration is not the first purchase you need to make.

There is one important exception, and it is the sort of thing that only shows up if you read the access page rather than the marketing page. The ChatGPT and Claude connectors are "available on all plans, including Free and Plus. No API key required". They still spend credits at the same rate as API calls. So the cheapest way to drive Gamma programmatically is not the API, and a team whose automation lives inside ChatGPT or Claude may not need to upgrade at all.

Those deck counts assume a bare 10-card generation with no AI images, costing 10 to 30 credits. Add images and the arithmetic changes completely, which is the next section.

What one API generation actually costs

Gamma bills two things separately. Cards are metered at 1 to 3 credits each, and the docs are candid that the rate "varies by the text generation model Gamma selects internally". You do not choose that model and the response does not tell you which one ran, so a 20-card deck lands anywhere between 20 and 60 credits with no way to predict which.

Images are where the real spread lives, and here you do choose. The four model tiers cost 2 to 15, 20 to 33, 34 to 75, and 30 to 125 credits per image respectively. Gamma sells top-up credits at 1,500 for $6, which fixes one credit at $0.004 and lets every rate above be read in dollars.

Put the two halves together and the shape of the bill is clear. Two hundred text-led decks a month costs somewhere around $8 to $36 in cards. The same two hundred decks with five premium images each costs up to $300 more. The images are the product, not the slides, and one line in your request body moves the invoice by a factor of forty.

Gamma's own worked scenarios say the same thing in its language: a 10-card deck with 5 basic images is "~20-60 credits", while a 20-card document with 15 premium images is "~320-1070 credits". That second range is worth staring at. It is one described document, and the high end costs more than three times the low end.

The costs that do not appear in the credit table

Three of them, all documented, none obvious.

Credits are assigned per user, not per workspace. The help center states that "each workspace member has their own balance", and an OAuth integration spends "the authorizing user's credits in the workspace they connected". If your automation authenticates as one service account, that account's monthly allowance is your real ceiling, regardless of how many seats you pay for.

One-time credit purchases are available "only in single-user workspaces". A team workspace that runs dry cannot simply buy a block of credits; it has to enable auto-recharge, which Gamma calls "the safest way to prevent failed generations due to exhausted credits". That is sound advice and it is also an uncapped spending commitment, so set the threshold deliberately.

Template-based generations cost more. The docs note that POST /generations/from-template "may cost slightly more per card than standard generations", without saying how much more. If your pipeline is built on a house template, which is the normal reason to automate in the first place, you are on the more expensive path by default.

One genuine credit in Gamma's favor: you are not billed for failures. The help center states plainly that "you will not be charged credits for errors or clarification requests", which matters when you are polling an async endpoint and retrying.

What the API gives you back

Generation is asynchronous. You POST to /v1.0/generations, get a generationId, and poll every five seconds until the status is completed or failed. The completed response carries gammaUrl, exportUrl and gammaId, plus a credits field showing deducted and remaining, which is the only place you learn what the call cost.

The export endpoint accepts exactly three values. exportAs is an enum of pdf, png and pptx, and that is the complete list. There is no Google Slides target, no Word, no Keynote, which matches what the product itself offers and is covered in more depth in our breakdown of Gamma to Google Slides. The endpoint also documents a 403 Feature not available for workspace, so export access is itself plan-dependent and worth testing on your actual tier before you build around it.

What the API does not change is what lands inside the .pptx. The same fidelity questions that apply to a manual export apply to an automated one, and they are the reason teams end up rebuilding decks by hand after generating them. The recurring failures are documented in why Gamma PowerPoint exports break.

Is automating this worth it at your volume

Run the comparison honestly before you build. An integration is engineering time up front plus a Pro seat or better, and it pays off when the deck is genuinely repetitive: a weekly client report, a monthly portfolio update, a templated sales one-pager. Below roughly a deck a week, the build will not earn its keep, and you are better off generating in the interface or, for genuinely bespoke client work, letting a freelance designer take the deck end to end.

The other honest answer is that an API is the right tool when the input is structured data and the wrong tool when the input is a document you already wrote. If the source is a finished report, proposal or PDF, you do not need a generation model to invent structure, you need the structure that is already there carried across. That is the case for a document-first route: upload the file, approve the extracted outline, and export a native .pptx with real editable text boxes and charts rebuilt from your own tables. Docslide does that on a flat subscription with no credit meter, so the cost of the hundredth deck is the same as the first. The seat-and-credit math for the interface side of Gamma is laid out on our Gamma pricing and credits page, and a feature-level comparison sits on the Gamma alternative page.

Does Gamma have a free API?

No. API keys require Pro or above, and the Free plan's credits do not refresh, so there is no sustainable free path to programmatic generation. The nearest thing is the ChatGPT or Claude connector, which works on every plan including Free without an API key, but it still spends credits at the same rate, and on Free those credits run out and stay out.

How do you keep API generations from failing mid-month?

Enable auto-recharge and watch the remaining value. Gamma returns credits.deducted and credits.remaining on every completed generation, so your integration already has the balance in hand. Log it, alert on a floor you choose, and set the auto-recharge threshold above the volume of a single busy day. Credits purchased while you are subscribed never expire, so a buffer costs nothing but the outlay.

The short version

Gamma's API is inexpensive for text and expensive for pictures, and the pricing page will not tell you that because the split lives in the developer docs. Price your pipeline by counting images first and decks second. Confirm your tier can issue an API key before you plan the work, remember that the credit balance belongs to a user rather than the workspace, and keep in mind that Gamma states its "credit consumption rates and the actions that consume credits are subject to change", so whatever you calculate today is a snapshot rather than a contract.