Deploy a subgraph
Deploy a compiled subgraph bundle as name/version.
Send multipart/form-data with a bundle file part — a zip of your graph build output. Bundles are limited to 50 MB compressed and 100 MB extracted.
Example: curl -X PUT -H "authorization: Bearer $GOLDSKY_API_KEY" -F bundle=@build.zip -F description="My subgraph" https://api.goldsky.com/api/v1/subgraphs/my-subgraph/deployments/1.0.0
Authorizations
API token generated from the Goldsky Dashboard. Pass as: Authorization: Bearer
Path Parameters
^[a-zA-Z][\w-]*$^[a-zA-Z0-9][\w+.-]*$Body
Send each option as an ordinary multipart/form-data field, e.g. -F overwrite=0. Fields appear below as { value } because that is how a form field looks once parsed.
Send each option as an ordinary multipart/form-data field, e.g. -F overwrite=0. Fields appear below as { value } because that is how a form field looks once parsed.
Zip of the compiled subgraph build directory (graph build output), sent as a file part.
Deprecated. Send "0" or omit it — "1" is rejected. To replace a version, delete it and deploy again, or move a tag to it.
Set to "1" to strip the graft from the manifest before deploying.
Set to "1" to skip validation of the graft base subgraph.
Block number to start indexing from.
name/version of an existing subgraph in this project to graft from.
Human-readable description (max 500 characters).
Advanced: pin the deployment to a specific indexing shard. Leave this unset unless Goldsky support asked you to set it.
Response
Default Response
ACTIVE HEALTHY Related topics
Deploy a subgraphCreate no-code subgraphsIndex onchain data with SubgraphsAgent SkillsSend subgraph-driven webhooks