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

# Core Operations Overview

> What GNet core is, which hosts it uses, how core routes read your token, and where each core operation is documented.

## What core is

**GNet core** is the GNet service that issues tokens and keeps company,
user, partner, and reservation records. The pages in this group document core
routes only.

Core is not the Connect API service. The Connect API service has its own base
URL and its own routes. It accepts tokens that core issues: it checks each
token with core `GET /api/token`. The legacy core content route
(`/api/content/{griddid}`) and the Connect API routes are not interchangeable.

## Hosts

| Environment | Core base URL |
| - | - |
| Production | `https://core.grdd.net` |
| Development | `https://core.grdd.dev` |

All paths in this group are relative to the core base URL, for example
`https://core.grdd.net/api/token`.

## Authentication

Get a token with [`POST /api/token`](/connect-api/get-token). The response
contains two credentials:

* `token`: a signed access token (JWT).
* `legacy`: a legacy token (a UUID string).

Send one of them on each core request:

```http theme={null}
Authorization: Bearer <token>
```

```http theme={null}
token: <legacy>
```

<Note>
  Use `Authorization: Bearer` with the access token. Every route in this group
  that reads a token accepts this form. One exception applies to tokens from
  partner impersonation; see
  [Partner Impersonation](/connect-api/core/partner-impersonation#use-the-token).

  Most core routes convert the value of the `token` header to lowercase before
  they use it. A signed access token does not survive that conversion, so on
  those routes the `token` header works only with the `legacy` value. The
  exception is `GET /api/token`, which also accepts the access token in the
  `token` header.

  Some partner actions accept only `Authorization: Bearer`. See
  [Manage Partners](/connect-api/manage-partners).
</Note>

The word `Bearer` is case-sensitive. Send it with a capital `B`.

## Response format

Core routes do not share one error format. Most routes return `success` and
`message`. The partner routes return `success` and `data.error`. Each page shows
the format of its route. Always check the `success` field as well as the HTTP
status.

## Operations

### Tokens

| Method and path | Page |
| - | - |
| `POST /api/token` | [Get Token](/connect-api/get-token) |
| `GET /api/token` | [Get Token](/connect-api/get-token#verify-a-token) |
| `DELETE /api/token` | [Get Token](/connect-api/get-token#release-a-token) |
| `POST /api/token/imp` | [Partner Impersonation](/connect-api/core/partner-impersonation) |

### Company and users

| Method and path | Page |
| - | - |
| `POST /api/company/register` | [Sign Up](/connect-api/sign-up) |
| `GET /api/user/check` | [User Check](/connect-api/user-check) |
| `PUT /api/company/edit` | [Edit User/Company](/connect-api/edit-company) |
| `GET /api/company/search`, `GET /api/company/{griddid}` | [Company Search](/connect-api/search) |

### Partners

| Method and path | Page |
| - | - |
| `POST /api/partner?action=...` | [Manage Partners](/connect-api/manage-partners) |
| `GET /api/partner`, `GET /api/partner/{griddid}` | [Get Partners](/connect-api/get-partners) |
| `GET /api/partner/isPartner`, `GET /api/partner/status` | [Get Partners](/connect-api/get-partners#check-one-partnership) |

### Reservations

| Method and path | Page |
| - | - |
| `GET /api/reservation/{transactionId}` | [Get Booking](/connect-api/bookings/get-booking) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.