---
title: "Call GitHub from a sandbox"
description: "Call the GitHub API from a sandbox with no token inside it."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.jgcp.mistrivedev.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Call GitHub from a sandbox

This program creates a sandbox with the GitHub integration attached, calls the GitHub API from inside it and prints the result. No GitHub token is in the program or the sandbox.

## How it works

1. The program creates a sandbox and attaches the GitHub integration.
2. A process in the sandbox calls `https://api.github.com/user` with `curl` and no `Authorization` header.
3. Sutra adds your organization's GitHub credential to the request after it leaves the VM, and GitHub answers as usual.
4. The program prints the response and deletes the sandbox.

## Why no token is needed

The credential never enters the sandbox. Code you run there, including code an agent writes, can call GitHub but cannot read the token, print it or send it anywhere else. When you remove the integration or your organization revokes it, the sandbox loses access at once.

See [Integrations and tool gateway](https://docs.jgcp.mistrivedev.com/platform/integrations/) for scopes and the tool gateway, and [Supported integrations](https://docs.jgcp.mistrivedev.com/platform/supported-integrations/) for the other providers you can call the same way.

Source: https://docs.jgcp.mistrivedev.com/examples/github-integration/index.mdx
