eCardWidget Developer API
67
AI ReadinessAI-Aware (B+)67/100
Official vendor OpenAPI document · agent-readyHR recruitingEmployee Managementbearer54 EndpointsREST
For Agents
Send eCards from a widget and keep a team-member directory in sync, plus manage reward gift cards, widgets, and automations for recognition programs.
Use for: Send an eCard to a team member from a widget, List the eCards available in a specific widget, Create or update a team member in the directory, Find a team member by their details
Not supported: Does not run payroll, track job applicants, or manage performance reviews. Use for sending eCards, syncing a team-member directory, and managing recognition rewards only.
The eCardWidget Developer API sends eCards and keeps a team-member directory in sync from your own systems such as HR, CRM, or donation platforms. It sends, schedules, or shares eCards from a widget, lists the eCards a widget offers, and upserts, finds, lists, deactivates, reactivates, or deletes team members along with their mappable fields and departments. It also manages reward gift-card settings, products, orders, and inventory, and the widgets and automations that drive recognition.
Install Jentic One Beta
Connect the eCardWidget Developer API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the eCardWidget Developer 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fecardwidget.com%2Fecardwidget" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fecardwidget.com%2Fecardwidget" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 eCardWidget Developer API.
Send, schedule, or share an eCard from a widget
List the eCards available in a widget and search eCard designs
Create or update team members and find or list them
Deactivate, reactivate, or permanently delete a team member
List the mappable fields and departments used to sync your directory
Manage reward gift-card settings, products, orders, and inventory
Create, search, duplicate, and delete widgets and toggle automations
Use Cases
Patterns agents use eCardWidget Developer API for, with concrete tasks.
★ Agent-driven recognition
An AI agent connected through Jentic sends an eCard to a team member from a chosen widget, for a birthday or work anniversary, after finding the member in the directory. The agent lists the eCards a widget offers, picks one, and sends it, so a recognition moment is handled without a person opening the dashboard.
Find a team member, list the eCards in a widget, and send one of them to that member
Directory sync from HR or CRM
Teams keep their eCardWidget team-member directory current by upserting members from an HR, HRIS, or CRM system and reading the mappable fields and departments to line the data up. The API exposes upsert, find, list, and deactivate operations plus a fields endpoint, so an agent can reconcile the directory against the source of truth.
List the mappable fields, then upsert a batch of team members from an HR export and deactivate anyone no longer present
Reward management
Recognition programs that attach gift-card rewards read the reward account settings, available products, orders, and inventory to run them. eCardWidget exposes gift-card settings, product list, orders, rules, and inventory endpoints so an agent can check what is available and what has been sent before issuing more.
List the available reward products and read the current reward rules and inventory before issuing a reward
Widget and automation management
Admins manage the widgets that hold eCards and the automations that trigger them by listing, searching, duplicating, and toggling them. The API exposes widget save, search, duplicate, and delete operations plus automation list and toggle, giving an agent control over how recognition is delivered.
Search the widgets, duplicate one with its eCards, and enable the automation attached to it
Key Endpoints
54 endpoints — the ecardwidget developer api sends ecards and keeps a team-member directory in sync from your own systems such as hr, crm, or donation platforms.
METHOD
PATH
DESCRIPTION
POST
/pub/ecard-actions/send-ecard
Send, schedule, or share an eCard
GET
/pub/ecard-actions/get-ecards
List eCards in a widget
POST
/pub/team-member-actions/upsert
Create or update a team member
GET
/pub/team-member-actions/list
List team members
GET
/gift-card/listProducts
List available reward products
GET
/widget/search
List or search widgets
GET
/key/info
Read what the API key is allowed to do
POST
/pub/ecard-actions/send-ecard
Send, schedule, or share an eCard
GET
/pub/ecard-actions/get-ecards
List eCards in a widget
POST
/pub/team-member-actions/upsert
Create or update a team member
GET
/pub/team-member-actions/list
List team members
GET
/gift-card/listProducts
List available reward products
GET
/widget/search
List or search widgets
GET
/key/info
Read what the API key is allowed to do
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
eCardWidget Developer API
- AI-Aware (B+)67/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility54
AI-Readiness & Agent Experience93
Agent Usability60
Security82
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
14%
Example Density
How richly the API is illustrated with examples.
88%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
54
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
58%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
56%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
82
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
82%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring eCardWidget by hand means handling its Bearer auth, checking the key-info endpoint for what a key can do, and running the upsert flow to reconcile your directory against an HR or CRM source yourself. Through Jentic you install once, import eCardWidget from the API Directory, store the token once, and your agent calls it.
Permission scoping
eCardWidget carries widget and automation ids in the URL path, while team-member actions carry the member in the request body, so a rule bounds which operations your agent may call, such as sending eCards and reading the directory. You choose the operations it may call, so destructive ones like permanently deleting a team member or a widget are not included unless you add them.
Credential isolation
Your eCardWidget token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send an eCard' or 'upsert a team member', and Jentic returns the matching eCardWidget operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using eCardWidget Developer API through Jentic.
What authentication does the eCardWidget API use?
The eCardWidget API authenticates with a Bearer token in the Authorization header per its OpenAPI spec, and a key-info endpoint reports what a given key is allowed to do. Through Jentic the token is stored once and injected at call time so it never enters the agent's prompt.
Can I send an eCard with the eCardWidget API?
Yes. You list the eCards a widget offers, then send, schedule, or share one through the send-eCard endpoint. The same widgets also hold the designs you can search and duplicate.
What are the rate limits for the eCardWidget API?
The OpenAPI spec does not publish fixed rate limits, but the gift-card endpoints expose velocity and spend limits with current usage for rewards. Check the eCardWidget documentation for the API limits that apply to your account.
Is there an eCardWidget API MCP server?
You don't need an MCP server to give your agent the eCardWidget API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent sends eCards and syncs the directory on demand without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the eCardWidget API?
Yes. Write a rule that allows only the send-eCard and team-member read operations, so the agent can send cards and read the directory but cannot permanently delete members or widgets, and every call it makes is logged for review.
How do I send recognition eCards with the eCardWidget API through Jentic?
Search Jentic for 'send an eCard', add the eCardWidget API from the directory, and store your token once; your agent can then find a team member and send them an eCard from a widget on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED