Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Credly (BYOK) icon

Credly (BYOK)

Read your Credly organization's digital badge templates, issued-badge states and counts, and recommendations with your own authorization token

Unify Dynamics LLC

Tools6read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderCredlyunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What is the profile of my Credly organization?
Tools called
get_organization
Which active badge templates does my organization have and how many badges were issued from each?
Tools called
list_badge_templates
Give me the details of one of my Credly badge templates
Tools called
get_badge_template
How many badges did we issue from template 9fc20758 since January and what state are they in?
Tools called
list_issued_badges
What is the state of issued Credly badge a1b2c3d4?
Tools called
get_issued_badge
What learning recommendations are set up in our Credly account?
Tools called
list_recommendations

About

Credly (BYOK) lets an AI assistant read your own Credly data through the Credly API with a key you supply (Credly organization authorization token). Read-only: 6 tools (get_organization, list_badge_templates, get_badge_template, list_issued_badges, get_issued_badge, list_recommendations). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.credly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Credly API (api.credly.com) with a BYOK key; documentation: https://docs.credly.com/browse/docs/getting-started. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

6 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data6 tools
  • Get organizationShow your Credly organization's profile: name, location, verification status, featured badge templates and whether it is a trial account.
  • List badge templatesList the organization's badge templates with state, visibility, number of badges issued, level, time to earn and skills.
  • Get badge templateGet one badge template: description, state, visibility, issue counts, level, time to earn, skills and public URL.
  • List issued badgesList badges issued by the organization with state, issue and expiry dates and their template.
  • Get issued badgeGet one issued badge by id: state, issue and expiry dates, visibility and its template.
  • List recommendationsList the learning recommendations configured in the organization (title, type, linked template count and last update).

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-credly.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-credly.connectorbay.com/mcp
RESTPOST https://byok-credly.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-credly.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Credly organization authorization token in the X-Upstream-Key header (get one at docs.credly.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Credly connector: questions and answers

What is the Credly connector?

Credly (BYOK) lets an AI assistant read your own Credly data through the Credly API with a key you supply (Credly organization authorization token). It is a hosted MCP server with 6 tools such as Get organization, List badge templates, Get badge template, List issued badges, Get issued badge, List recommendations, published by Unify Dynamics LLC. It is independent and not affiliated with Credly.

How do I connect Credly to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-credly.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-credly.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-credly.json.

Do I need a Credly account or API key?

Yes: this is a bring-your-own-key connector. Create a Credly organization authorization token at https://docs.credly.com/browse/docs/authentication-methods and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Credly read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Credly connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Braze (BYOK)

Read your Braze campaigns, Canvases, segments, custom events, user trend series and email templates with your own REST API key

Live · MCP + REST10 tools

Breezy HR (BYOK)

Read your Breezy HR companies, positions, departments, hiring pipelines, questionnaires and message templates (no candidate data) with your own personal access token

Live · MCP + REST10 tools

Brella (BYOK)

Read your Brella event-networking data: events, schedule sessions, tracks, sponsors, ticket types, announcements and event, ticket-sales and session analytics with your own organization token

Live · MCP + REST12 tools

Brevo (BYOK)

Read your Brevo account, contacts, lists, segments, email campaigns and their statistics, senders and templates with BYOK

Live · MCP + REST8 tools

Brevo Setup (BYOK)

Read your Brevo sending domain authentication status, dedicated IPs, webhooks, contact attribute definitions, folders and consent groups with your own API key (no contacts)

Live · MCP + REST8 tools

Brevo SMS and WhatsApp (BYOK)

Read your Brevo SMS campaigns, WhatsApp campaigns and templates, WhatsApp account status and transactional SMS aggregate reports with your own API key (no recipients or message text)

Live · MCP + REST9 tools

Documentation

Back to top

Credly (BYOK) — connector documentation

  • MCP endpoint: https://byok-credly.connectorbay.com/mcp
  • REST API: POST https://byok-credly.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-credly.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Credly Credly organization authorization token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-credly.connectorbay.com/health · Tool schemas: https://byok-credly.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-credly · agent@connectorbay.com

What Credly (BYOK) is for

Credly (BYOK) lets an AI assistant read your own Credly data through the Credly API with a key you supply (Credly organization authorization token). Read-only: 6 tools (get_organization, list_badge_templates, get_badge_template, list_issued_badges, get_issued_badge, list_recommendations). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.credly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What is the profile of my Credly organization?"
  • "Which active badge templates does my organization have and how many badges were issued from each?"
  • "Give me the details of one of my Credly badge templates"
  • "How many badges did we issue from template 9fc20758 since January and what state are they in?"
  • "What is the state of issued Credly badge a1b2c3d4?"
  • "What learning recommendations are set up in our Credly account?"

What it does

  • get_organization: Show your Credly organization's profile: name, location, verification status, featured badge templates and whether it is a trial account.
  • list_badge_templates: List the organization's badge templates with state, visibility, number of badges issued, level, time to earn and skills. Filter by state or name.
  • get_badge_template: Get one badge template: description, state, visibility, issue counts, level, time to earn, skills and public URL.
  • list_issued_badges: List badges issued by the organization with state, issue and expiry dates and their template. Recipient names and emails are left out of the answer. Filter by state, template or creation date.
  • get_issued_badge: Get one issued badge by id: state, issue and expiry dates, visibility and its template. Recipient details are left out.
  • list_recommendations: List the learning recommendations configured in the organization (title, type, linked template count and last update).

BYOK key

You bring your own Credly Credly organization authorization token (https://docs.credly.com/browse/docs/authentication-methods). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.credly.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Credly API (api.credly.com) with a BYOK key; documentation: https://docs.credly.com/browse/docs/getting-started. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Credly account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Credly (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Credly (BYOK) is. Credly (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Credly data: Read your Credly organization's digital badge templates, issued-badge states and counts, and recommendations with your own authorization token. You bring your own Credly Credly organization authorization token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Credly call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.credly.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Credly rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Credly receives. The request we make on your behalf, including the key and the arguments, under Credly's own terms and privacy policy. Credly acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Credly gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Credly data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Credly (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Credly at any time to end all access.

Children. Credly (BYOK) is a general-audience service operated by the adult using the assistant, under Credly's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Credly (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Credly (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Credly (BYOK) provides: Read your Credly organization's digital badge templates, issued-badge states and counts, and recommendations with your own authorization token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Credly credentials and only access data you are allowed to access. Credly's terms apply to your use of Credly; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Credly returns, lightly trimmed; it may be incomplete, delayed or changed by Credly. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Credly account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Credly's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Credly may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Credly key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Credly takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-credly

Credly (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Credly (BYOK) never asks for them.

Get Credly (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Credly Credly organization authorization token. Create one at https://docs.credly.com/browse/docs/authentication-methods, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Credly. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Credly.