canonical: https://jentic.com/apis/glibl.fr/glibl

# Glibl Fr Glibl

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.

## For AI agents

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

## Scope

Does not handle deal pipelines, marketing automation, or email verification - use for digital business card contact capture and team card-sharing analytics only.

## Capabilities

- 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
- Pull card-share and card-visit statistics to measure how a sales rep's digital card is performing
- Read team-wide aggregated counters (without raw data) for manager-level reporting

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Contacts** — Add new digital business card contacts and toggle favourite status.
- **Collaborator Contacts** — Retrieve contacts and contact-creation counts for collaborators under a team manager.
- **Collaborator Statistics** — Card share and card visit metrics per user or team.
- **Profile and User** — Read the authenticated user's profile and credentials.
- **Team Manager** — Aggregate team statistics and release notes for the Team Manager product.

## Why Jentic

- **Setup:** Wiring Glibl by hand means running its OAuth2 authorization-code flow, managing the client id and secret, and refreshing tokens yourself. Through Jentic you install once, import the Glibl API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Glibl puts the collaborator id in the URL path (`/v4/collaborator-stats/card-visits/{c_id}`), so a rule can pin your agent to one collaborator: it can read that collaborator's card-share and visit stats and nothing else. You choose the operations it may call, so it adds contacts or toggles favourites only when you include those operations.
- **Credential handling:** Your Glibl OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a business card contact' or 'get card visit stats', and Jentic returns the matching Glibl operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **HubSpot CRM Contacts** — Full-featured CRM contact store versus Glibl's business-card-first capture flow.
- **Pipedrive API** — Pipeline CRM that pairs with Glibl when captured cards graduate into deals.
- **Hunter API** — Email finder and verifier that enriches Glibl-captured contacts with verified work emails.

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Glibl API?

Yes. Because you run Jentic One yourself, your own rules decide which Glibl operations the agent may call, so you can grant read-only access to card-share and card-visit stats while withholding write operations like POST `/v4/contact/add` or PATCH `/v4/contact/togglefavorite.` Glibl puts the collaborator id in the URL path, such as `/v4/collaborator-stats/card-visits/{c_id}`, so a rule can pin the agent to a single collaborator and let it read only that person's stats and nothing else. Your OAuth client id and secret are held by your own instance and injected at execution time, never entering the agent's context.