Ezequiel B.

We have also noticed that older presentations previously generated via the API now require the user to be logged into Gamma in order to edit them. We are not claiming with certainty that it was different before, but based on our workflow and tests, this appears to be a recent change. When accessing those older editable links in incognito mode (without logging in), editing is no longer possible. Could you please clarify whether this behavior is the result of a recent update, or if this was always the intended functionality?

Urgent – External Editing Access Not Working via API Hello Gamma Support Team, I hope you are doing well. I’m reaching out because we are experiencing an urgent issue with the Gamma API related to external editing permissions. We are generating presentations programmatically via n8n using the Gamma API. In our HTTP request, we are explicitly setting the sharingOptions to allow external users to edit the generated document. However, when we receive the generated link, the user is not able to edit. Instead, Gamma displays a screen asking the user to join our workspace in order to access editing. This is the JSON payload we are currently sending:

{
  "gammaId": "g_rdd1fs0ll3bsfdq",
  "prompt": "[here put all the information about the wine]. In the top-right area of the header, replace the existing template logo with the provided logo URL. On the left side of the A4 layout, replace the placeholder image with the provided wine image URL. Make sure both images are always replaced.",
  "exportAs": "pdf",
  "sharingOptions": {
    "workspaceAccess": "fullAccess",
    "externalAccess": "edit"
  }
}

Our expectation is that when externalAccess is set to "edit", the recipient should be able to edit the presentation without requiring workspace membership. However, the current behavior forces them to request access or join our workspace, which interrupts our automated workflow. Could you please confirm:

This feature is essential for our workflow, as users need to be able to edit the generated documents directly after creation, without manual invitation steps. Thank you in advance for your help. We appreciate your support and look forward to your guidance. Max J.

Max J.

I'm encountering a critical issue with the Gamma API that's blocking my integration. I'm receiving an error that doesn't align with the documented API behavior. The Problem: I'm getting this error message:

Bad request - please check your parameters
Input validation errors: 1. imageModel must be one of: dall-e-3, imagen-2, [...list of models...]

What I'm Trying to Do: According to the API documentation, I should be able to create a gamma with no images by setting: json

"imageOptions": {
  "source": "noImages"
}

The Issue: Despite explicitly specifying "source": "noImages" in my imageOptions, the API is still requiring me to provide an imageModel parameter. This makes no sense—if I'm telling the API I don't want any images, why is it demanding that I specify which image generation model to use? Expected Behavior: When I use "source": "noImages", the API should:

Current Behavior: The API rejects my request and demands an image model, even though I've explicitly stated I don't want images. Questions:

This is preventing me from using the API as documented. Please advise on how to proceed.