β‘Running glifs via the API
The Glif API is unstable and in limited beta, but weβre excited to see what y'all build.
To get started, create your API tokens on https://glif.app/settings/api-tokens
The API is currently free with the same rate limits as normal user accounts; see FAQ details. This is all subject to change without notice.
Additionally, API users may not run glifs that use any of the following models: StableDiffusion 3, DALL-E 3, Flux Pro, and Flux Dev; or Flux Dev via comfyBlock. Please make sure to follow these rules as we'll otherwise have to revoke your API access.
If you're building with our API, please join our Discord or get in touch since we'd love to chat and learn more about what you're building. For selected apps we can extend a higher rate limit during this free testing period.
We ask that you include βpowered by glif.appβ and a link to glif.app within the UI of your integration. Please use a Glif logo badge in the zip file below.
Running glifs using the Simple API
The Simple API requires an API token to make requests
Hereβs the expected output of that command:
You're most likely interested in the output
field, which is the final output of the glif.
outputFull
is a JSON object with more info about the final output, including it's type.
If thereβs an error itβll be in an error
field, but the response will have a "200 OK" status code. For legacy reasons the the Simple API always returns 200 OK. This might change in the future.
Parameters
id
You can put the glif id in the url:
Or put it in the body:
inputs
for now only string values are allowed
You can either use a positional array:
Or name your parameters. The names have to correspond to your glif-block names. If you don't know the block names, check out Looking up the internal names of a glif's inputs.
Looking up the internal names of a glif's inputs
To specify named parameters, you need to use the internal block name. This has no spaces and usually is something like "text1", "multipick2", but each glif creator can customize it.
On the glif.app website you can look at the block names in the "View source" page of a glif, like this one:
Or you can look at the nodes
field of a glif's data via our API:
https://glif.app/api/glifs?id=clkbasluf0000mi08h541a3j4 This glif has blocks with the names:
Lastly, you can use the commandline to fetch field names dynamically using curl
+ jq
:
here's the output:
meaning this glif requires two inputs, input1
and image1
. We plan to improve this in the near future.
β οΈ Strict mode and default glif input value substitution
If you do not provide enough inputs, the default values in the glif values will be automatically substituted.
So if you specify arg1, that'll be used, but if it requires arg1 and arg2, it'll use your arg1 but use the defualt value for arg2.
If you'd prefer to have API calls with insufficient inputs to fail, append ?strict=1
to your URLs, e.g. https://simple-api.glif.app?strict=1
β οΈ CORS (cross-origin requests)
CORS is allowed by the Simple API, but not by our other API endpoints. You'll need to make your own serverside wrappers for these cases.
Last updated