GoLinks API

Name: GoLinks API
Brand: GoLinks API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbearer8 EndpointsREST

For Agents

Create, update, and look up internal go/links and read their daily redirect metrics across a GoLinks workspace.

Connect the GoLinks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoLinks API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GoLinks API.

Create a memorable go/link that resolves to a long internal URL

Edit the destination of an existing go/link without changing its short name

List every go/link in the workspace with pagination support

Retrieve daily redirect metrics for usage and adoption reporting

GET STARTED

Start building with GoLinks API

Explore with Jentic

View OpenAPI Document

Use for: Create a go/link called go/handbook that resolves to our Notion company handbook, I want to update go/onboarding to point to the new 2026 onboarding doc, List all go/links created in the last quarter, Retrieve the daily redirect counts for the engineering team's go/links

Not supported: Does not handle public branded short links, click fraud detection, or QR-code generation — use for internal company go/link CRUD, redirect metrics, and workspace user lookup only.

Use Cases

Patterns agents use GoLinks API for, with concrete tasks.

★ Internal Knowledge Routing

Engineering and operations teams use GoLinks to give every important internal resource a short, memorable handle (go/oncall, go/handbook, go/runbook). The API lets platform teams script bulk creation during onboarding, keep destinations fresh as docs move, and audit unused links — all without manual editing in the GoLinks UI.

Create the go/links go/handbook, go/oncall, and go/runbook pointing to the matching Notion and PagerDuty URLs.

Adoption Reporting

Platform teams measure how widely internal documentation is reaching the company by pulling the daily redirect metrics endpoint into a dashboard. Low-traffic links flag stale or undiscovered docs, while spikes reveal the resources actually driving day-to-day work.

Pull the last 30 days of redirect metrics from /metrics/redirects and produce a CSV of the top 20 most-used go/links.

Lifecycle Cleanup of Stale Links

Over time a workspace accumulates go/links pointing to deprecated dashboards or archived projects. The API's list, retrieve, and delete operations let an automation script enumerate every link, check redirect counts, and prune anything below a threshold so the namespace stays trustworthy.

List every go/link, find ones with zero redirects in the last 90 days, and delete them.

AI Agent Resource Lookup via Jentic

An AI assistant answering employee questions can resolve go/links to their canonical destinations before fetching the underlying doc, so 'what's go/handbook?' returns the live URL rather than a stale answer. Through Jentic the agent searches by intent, loads the GET /golinks/{name} schema, and executes against the workspace bearer token held in the vault.

Look up the go/link named 'handbook' and return the destination URL it currently resolves to.

Key Endpoints

8 endpoints — the golinks api provides 8 endpoints for managing go/links — short, memorable internal urls that resolve to long company resources such as docs, dashboards, and runbooks.

METHOD

PATH

DESCRIPTION

GET

/golinks

List all golinks

POST

/golinks

Create a golink

GET

/golinks/{name}

Retrieve a golink by name

PUT

/golinks/{name}

Edit a golink

DELETE

/golinks/{name}

Delete a golink

GET

/metrics/redirects

Daily redirect metrics

GET

/users/search

Search workspace users

GET

/golinks

List all golinks

POST

/golinks

Create a golink

GET

/golinks/{name}

Retrieve a golink by name

PUT

/golinks/{name}

Edit a golink

DELETE

/golinks/{name}

Delete a golink

GET

/metrics/redirects

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

GoLinks bearer tokens are stored encrypted in the Jentic vault (MAXsystem) and scoped to a single workspace. Agents receive a short-lived execution handle, so the raw token never appears in the model context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create an internal go link') and Jentic returns the GoLinks /golinks operation with its input schema, so the agent can call it without reading the API reference.

Time to first call

Direct GoLinks integration: a few hours for auth setup and request plumbing. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using GoLinks API through Jentic.

What authentication does the GoLinks API use?

The GoLinks API uses bearer token authentication (bearerAuth) on the Authorization header. Tokens are workspace-scoped, and through Jentic they are stored encrypted in the vault so the raw token never enters the agent's context.

Can I create a go/link with the GoLinks API?

Yes. POST /golinks accepts a name and a destination URL, and the link is immediately resolvable from go/{name} inside the workspace. Use GET /golinks/{name} first if you need to check that the name is free.

What are the rate limits for the GoLinks API?

GoLinks applies per-workspace rate limits documented at help.golinks.io. The OpenAPI spec does not encode exact numbers, so check the GoLinks support docs before running bulk imports of more than a few hundred links.

How do I report on go/link usage through Jentic?

Search Jentic for 'go link redirect metrics', load the schema for GET /metrics/redirects, and execute. Jentic injects the bearer token at execution and returns the daily redirect counts so an agent can build adoption dashboards without writing an HTTP client.

Can the API list users in my workspace?

Yes. GET /users returns every user in the GoLinks workspace and GET /users/search filters by query string, which is useful for matching go/link owners to people during audits.

Does the GoLinks API support public short links like bit.ly?

No. GoLinks resolves only inside the company workspace and the API only manages internal go/links. For public-facing branded short URLs use Bitly or Rebrandly instead.

GoLinks API

Connect the GoLinks API to your agent

Capabilities

Start building with GoLinks API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs