# Create a runner registration token for a workspace

> A registration token for g1t-runner register, shown once.

<div class="g1t-endpoint"><span class="g1t-method" data-method="post">POST</span><code>/workspaces/{workspace}/actions/runners/registration-token</code></div>

It lasts an hour and registers any number of runners until then, into `group` (the default group if none) for a workspace, or as a repository's own runners. It can do nothing else. Owners of the workspace, or admins of the repository, signed in or with a person's token; workspace tokens, G1T_TOKEN included, are refused.

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`workflow`](/reference/mcp/#workflow) with `action` `create_runner_token`, and the same inputs
- **Scope:** An access token needs [`runners:admin`](/guides/authentication/#scopes).
- **Also at:** [`POST /repos/{owner}/{name}/actions/runners/registration-token`](/reference/api/runners/create-runner-registration-token/)

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `workspace` | string | Yes | Instead of repo: the workspace, for the runners its repositories share. |

## Body parameters

Send a JSON object. Names are `snake_case`, as in responses; the `camelCase` spelling is accepted too.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `group` | string | No | A workspace's runner group, by name or id, for the runners it registers. The default group if left out. |

## Example request

```sh
curl -X POST https://api.g1t.sh/workspaces/flagon-io/actions/runners/registration-token \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "group": "Default"
  }'
```

## Example response

A successful request answers `200` with:

```json
{
  "token": "g1trt_…",
  "expires_at": "2026-10-06T15:04:00.000Z",
  "workspace": "flagon-io",
  "repo": null,
  "group": "Default",
  "url": "https://g1t.sh"
}
```

## Errors

A failed request answers with one of these statuses and a body like `{"error": {"code": "not_found", "message": "Repository not found."}}`. See [errors](/reference/api/#errors).

| Status | Code | When |
| --- | --- | --- |
| 401 | `unauthenticated` | A token is required, or the one sent is not valid. |
| 403 | `forbidden` | The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository. |
| 404 | `not_found` | It does not exist, or you cannot see it. |
| 409 | `conflict` | The request conflicts with the current state. |
| 422 | `invalid` | The input is not valid. `message` says which field and why. |