Glibl

Name: Glibl API
Brand: Glibl
Availability: InStock

✓ Official Vendor SpecCRMContact Managementoauth214 EndpointsREST

For Agents

Manage Glibl digital business card contacts, retrieve team sharing statistics, and track card visit metrics for managers and collaborators.

Connect the Glibl to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Glibl, 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 Glibl API.

Add a new contact captured from a digital business card to a collaborator's address book

Retrieve every contact collected across a team manager's collaborators in one call

Mark a Glibl contact as a favourite or unfavourite via the togglefavorite endpoint

Fetch monthly contact-creation counts for a specific collaborator to drive sales activity dashboards

GET STARTED

Start building with Glibl API

Explore with Jentic

View OpenAPI Document

The Glibl API powers a digital business card platform that lets professionals and teams digitise paper business cards and capture contacts on the go. Through this API, applications can fetch contacts collected by team members, log new contacts captured via shared cards, track sharing and visit statistics for each card, and inspect team-level activity. Access requires a partner-issued OAuth 2.0 client; Glibl provisions CLIENT_ID and SECRET_ID after reviewing third-party application requests.

Use Cases

Patterns agents use Glibl API for, with concrete tasks.

★ Field Sales Contact Capture

Sales reps scanning paper business cards at events can have those contacts pushed straight into Glibl via the /v4/contact/add endpoint, keeping a single shared address book for the team. The API lets the capture app send name, company, email, phone and notes in one call, then the manager retrieves everything via /v4/collaborator-contact-all. Integration is typically a few hours once the OAuth 2.0 client is provisioned.

Call POST /v4/contact/add with the captured business card fields and confirm the new contact ID in the response.

Sales Manager Activity Dashboard

Sales managers need to see how active each rep is - new contacts logged this month, cards shared, and card visits received. The Glibl stats endpoints (/v4/collaborator-stats/card-shares, /v4/collaborator-stats/card-visits, /v4/collaborator-contact/count-per-month) return the counters needed to populate dashboards without exposing raw contact data. A weekly cron job can refresh a BI tool in under a minute per team.

Fetch GET /v4/collaborator-contact/count-per-month/{c_id} and GET /v4/collaborator-stats/card-shares/{c_id} for each rep ID and aggregate into a manager dashboard.

AI Agent Contact Sync

An AI assistant given access to Glibl through Jentic can answer questions like "how many new contacts did Alice add last month?" or "mark Bob's contact as a favourite" by routing to the right Glibl endpoint. Because Glibl provisions OAuth credentials manually, Jentic's vault holds the access token and the agent never sees the CLIENT_ID or SECRET_ID directly.

Search Jentic for 'list business card contacts', load the Glibl /v4/collaborator-contact-all schema, execute it for the manager's company ID, and summarise the latest 10 contacts.

Key Endpoints

14 endpoints — the glibl api powers a digital business card platform that lets professionals and teams digitise paper business cards and capture contacts on the go.

METHOD

PATH

DESCRIPTION

POST

/v4/contact/add

Add a new digital business card contact

GET

/v4/collaborator-contact-all

List every contact across a team manager's collaborators

GET

/v4/collaborator-contact/count-per-month/{c_id}

Monthly contact creation statistics

GET

/v4/collaborator-stats/card-shares/{c_id}

Card sharing statistics for a user or team

GET

/v4/collaborator-stats/card-visits/{c_id}

Card visit statistics for a user or team

PATCH

/v4/contact/togglefavorite

Mark a contact as favourite or remove favourite

POST

/v4/contact/add

Add a new digital business card contact

GET

/v4/collaborator-contact-all

List every contact across a team manager's collaborators

GET

/v4/collaborator-contact/count-per-month/{c_id}

Monthly contact creation statistics

GET

/v4/collaborator-stats/card-shares/{c_id}

Card sharing statistics for a user or team

GET

/v4/collaborator-stats/card-visits/{c_id}

Card visit statistics for a user or team

Why Jentic?

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

Credential isolation

Glibl OAuth 2.0 CLIENT_ID and SECRET_ID are stored encrypted in the Jentic vault. Agents receive a scoped access token at execution time - the raw client secret never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent ('add a business card contact', 'card visit stats') and Jentic returns the matching Glibl operation with its input schema, removing the need to read Glibl's documentation.

Time to first call

Direct Glibl integration: 1-2 days waiting for partner credentials plus OAuth token-refresh handling. Through Jentic: under an hour once the credential is loaded into the vault.

FAQs

Specific to using Glibl API through Jentic.

What authentication does the Glibl API use?

Glibl uses OAuth 2.0 and does not allow self-service application creation. You must email contact@glibl.fr to be issued a CLIENT_ID and SECRET_ID, then exchange them for a bearer token on each request. Through Jentic the OAuth credentials are stored in the vault so the agent never sees them directly.

Can I add new business card contacts through the Glibl API?

Yes. POST /v4/contact/add creates a new contact in the authenticated user's address book, and PATCH /v4/contact/togglefavorite flips the favourite flag for an existing contact.

What are the rate limits for the Glibl API?

Glibl does not publish a documented rate limit in its OpenAPI spec. Treat it as a partner-tier API and cache statistics endpoints aggressively rather than polling per request.

How do I retrieve a sales rep's contact count through Jentic?

Search Jentic for 'monthly contact count' or 'glibl collaborator stats', load the schema for GET /v4/collaborator-contact/count-per-month/{c_id}, and execute with the collaborator's ID. Run pip install jentic to start.

Does the Glibl API expose individual card visit events?

No. The /v4/collaborator-stats endpoints return aggregated counters (totals and monthly breakdowns) rather than per-visit event records, which is suitable for dashboards but not for full event streaming.

Is the Glibl API free to use?

Glibl does not advertise public API pricing. Access is gated by a partner application review, so commercial terms are negotiated when CLIENT_ID and SECRET_ID are issued.