Gyazo API
Agent-ready OpenAPI document · curated by JenticMediaImage Processingbearer5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Upload, list, search, retrieve, and delete screenshots and images in a Gyazo user library through five REST endpoints.
Use for: Upload a screenshot to Gyazo, List the most recent images in my Gyazo library, Search my Gyazo images for ones that match a query, Retrieve the metadata for a specific Gyazo image
Not supported: Does not handle video transcoding, image transformation, or DRM - use for personal-account screenshot upload, listing, search, and deletion only.
Jentic publishes the only available OpenAPI specification for Gyazo API, keeping it validated and agent-ready. Gyazo is a screenshot and image-sharing tool, and its API exposes the user's image library for programmatic upload, listing, retrieval, deletion, and search. The five-endpoint surface lets developers automate screenshot capture flows, build moderation tooling, or pull images into downstream apps. Authentication is via bearer access token tied to a Gyazo user account.
Install Jentic One Beta
Connect the Gyazo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gyazo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgyazo.com%2Fgyazo" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgyazo.com%2Fgyazo" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Gyazo API.
Upload an image to a Gyazo user account and receive the public share URL
List the authenticated user's image library with pagination
Retrieve a single image record by image ID
Search a user's images by query string
Delete an image from a Gyazo account by image ID
Use Cases
Patterns agents use Gyazo API for, with concrete tasks.
★ Automated screenshot capture pipeline
Capture screenshots from a desktop or browser-automation flow and post them to Gyazo to obtain a shareable URL for embedding in support tickets, bug reports, or release notes. The upload endpoint accepts the binary file and returns the canonical permalink, which downstream systems then store on the bug record.
POST /api/upload with the screenshot file and store the returned permalink on the matching ticket record.
Personal image library audit
List the authenticated user's Gyazo library to audit historical screenshots - for example before changing employer or cleaning up sensitive captures. The list and search endpoints support pagination and query filtering, and the delete endpoint removes images that should no longer be public.
GET /api/images with paging, filter the results by capture date, and DELETE matching image IDs after user approval.
Knowledge-base screenshot ingestion
A documentation tool searches an author's Gyazo account for the relevant screenshots when generating a knowledge-base article and embeds them by permalink. The search endpoint returns image IDs and URLs that the doc tool inserts into the article body without manual download and re-upload.
GET /api/search with query 'login screen' and embed the top three results into the article draft.
AI agent screenshot helper via Jentic
An AI assistant captures a UI screenshot during a tutorial-creation flow, uploads it to Gyazo, and inserts the returned permalink into the generated tutorial markdown. Through Jentic the agent calls the upload endpoint without managing the SDK.
Search Jentic for 'upload a screenshot to gyazo', load POST /api/upload, and execute with the captured image bytes.
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for gyazo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/images
List user's images
GET
/api/images/{image_id}
Get image by ID
DELETE
/api/images/{image_id}
Delete an image
POST
/api/upload
Upload an image
GET
/api/search
Search images
GET
/api/images
List user's images
GET
/api/images/{image_id}
Get image by ID
DELETE
/api/images/{image_id}
Delete an image
POST
/api/upload
Upload an image
GET
/api/search
Search images
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Gyazo API by hand means handling its bearer access token and splitting calls between the api.gyazo.com and upload.gyazo.com hosts while managing retries yourself. Through Jentic you install once, import Gyazo from the API Directory, store the token once, and your agent calls it.
Permission scoping
Gyazo puts the image id in the URL path (/api/images/{image_id}), so a rule can pin your agent to one image: it can fetch that image and nothing else. You choose the operations it may call, so deleting an image is not included unless you add it.
Credential isolation
Your Gyazo access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'upload a screenshot to Gyazo' or 'search my images', and Jentic returns the matching operation with its input schema, including the image-file field, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Gyazo API through Jentic.
Why is there no official OpenAPI spec for Gyazo API?
Gyazo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Gyazo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Gyazo API use?
Gyazo uses HTTP bearer authentication with an access token issued from the user's Gyazo account. Pass it as Authorization: Bearer <token>. Through Jentic, the token is stored encrypted in the vault and only scoped tokens are passed to the executing agent.
Can I upload a screenshot programmatically with the Gyazo API?
Yes. POST /api/upload accepts the image file and returns the canonical permalink for the new image record. This is the same endpoint the Gyazo desktop client uses internally.
Can I search my Gyazo library by query with the Gyazo API?
Yes. GET /api/search returns image records that match the query string, scoped to the authenticated user's library. Combine it with GET /api/images for paginated browsing of the full library.
What are the rate limits for the Gyazo API?
Gyazo applies user-account rate limits typically measured in tens of requests per minute on the free tier with higher limits for paid plans. Back off on 429 responses and avoid bulk-deleting an entire library in one tight loop.
How do I upload a screenshot through the Gyazo API via Jentic?
Search Jentic for 'upload a screenshot to gyazo', load the POST /api/upload operation, then execute with the image bytes. Install with pip install jentic.
Can I limit what my agent is allowed to do with the Gyazo API?
Yes. Because you self-host Jentic One, your own rules decide which of the five Gyazo operations the agent may call, so you can grant it upload and search while excluding DELETE /api/images/{image_id} unless you explicitly add it. Since the image id sits in the URL path, a rule can pin the agent to a single image so it retrieves that one record and nothing else. Your Gyazo access token stays under your control and is only injected for the operations you have allowed.
GET STARTED