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 coreGET /api/token. The legacy core content route
(/api/content/{griddid}) and the Connect API routes are not interchangeable.
Hosts
All paths in this group are relative to the core base URL, for example
https://core.grdd.net/api/token.
Authentication
Get a token withPOST /api/token. The response
contains two credentials:
token: a signed access token (JWT).legacy: a legacy token (a UUID string).
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.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.Bearer is case-sensitive. Send it with a capital B.
Response format
Core routes do not share one error format. Most routes returnsuccess 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.