Hallmark Cards website screenshot

Hallmark Cards

Hallmark Cards, Inc. is a privately held, family-owned greeting card, gift, gift wrap and ornament company headquartered in Kansas City, Missouri, founded in 1910 by J.C. Hall. Its portfolio spans Hallmark greeting cards and Keepsake Ornaments sold through Hallmark Gold Crown stores and mass retailers, the Crayola and Hallmark Business Connections (B2B greeting card programs) subsidiaries, and Hallmark Media (Hallmark Channel, Hallmark+). Hallmark publishes no public developer program: developer.hallmark.com does not resolve, api.hallmark.com serves a stock ASP.NET template with no documented endpoints, and no OpenAPI, GraphQL, MCP, A2A agent card, llms.txt or /.well-known discovery document was found on any Hallmark host on 2026-09-17. Retail and supply-chain partners integrate through bilateral EDI (Hallmark Global Services) and Hallmark Business Connections' CRM/SSO integrations, none of which are documented publicly.

Hallmark Cards is profiled on the APIs.io network. Tagged areas include Greeting Cards, Gifts, Retail, Consumer Goods, and Stationery.

Hallmark Cards’ developer surface includes engineering blog, support, and 17 more developer resources.

11.0/100 emerging ▬ flat Agent 3/100 human only Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-04 · rubric v0.23.0
0 APIs
Greeting CardsGiftsRetailConsumer GoodsStationeryGift WrapMediaBusiness GreetingsFortune 1000

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-04 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hallmark-cards: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hallmark Cards Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hallmark Cards Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 9

The organization behind the API

Scroll for all 9

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hallmark-cards
url: https://raw.githubusercontent.com/api-evangelist/hallmark-cards/refs/heads/main/apis.yml
name: Hallmark Cards
type: Index
kind: company
position: Consuming
access: 3rd-Party
x-api-posture: no-product-api
x-api-posture-basis: observed
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-09-17'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: No public API program
  confidence: high
  source:
  - researched
  generated: '2026-09-17'
  method: researched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hallmark-cards.png
tags:
- Greeting Cards
- Gifts
- Retail
- Consumer Goods
- Stationery
- Gift Wrap
- Media
- Business Greetings
- Fortune 1000
tags_raw:
- Greeting Cards
- Gift
- Retail
- Consumer Goods
- Stationery
- Gift Wrap
- Media
- Business Greetings
- Fortune 1000
description: 'Hallmark Cards, Inc. is a privately held, family-owned greeting card, gift, gift wrap and ornament company headquartered
  in Kansas City, Missouri, founded in 1910 by J.C. Hall. Its portfolio spans Hallmark greeting cards and Keepsake Ornaments
  sold through Hallmark Gold Crown stores and mass retailers, the Crayola and Hallmark Business Connections (B2B greeting
  card programs) subsidiaries, and Hallmark Media (Hallmark Channel, Hallmark+). Hallmark publishes no public developer program:
  developer.hallmark.com does not resolve, api.hallmark.com serves a stock ASP.NET template with no documented endpoints,
  and no OpenAPI, GraphQL, MCP, A2A agent card, llms.txt or /.well-known discovery document was found on any Hallmark host
  on 2026-09-17. Retail and supply-chain partners integrate through bilateral EDI (Hallmark Global Services) and Hallmark
  Business Connections'' CRM/SSO integrations, none of which are documented publicly.'
created: '2026-04-19'
modified: '2026-09-17'
specificationVersion: '0.23'
apis: []
common:
- type: Website
  url: https://www.hallmark.com
- type: About
  url: https://corporate.hallmark.com/
- type: Newsroom
  url: https://corporate.hallmark.com/hallmark-news/news/
- type: BlogRSS
  url: https://corporate.hallmark.com/feed/
- type: Blog
  url: https://ideas.hallmark.com/
- type: BlogRSS
  url: https://ideas.hallmark.com/feed/
- type: Support
  url: https://care.hallmark.com/s/
- type: Careers
  url: https://careers.hallmark.com/
- type: Partners
  url: https://corporate.hallmark.com/business-opportunities/
- type: X-Suppliers
  url: https://corporate.hallmark.com/citizenship/hallmark-community/supplier-partnerships/
- type: X-BusinessSolutions
  url: https://www.hallmarkbusiness.com/
- type: PrivacyPolicy
  url: https://www.hallmark.com/privacy/
- type: TermsOfService
  url: https://www.hallmark.com/terms-of-use/
- type: LinkedIn
  url: https://www.linkedin.com/company/hallmark-cards
- type: DomainSecurity
  url: security/hallmark-cards-domain-security.yml
- type: X-WellKnownProbe
  url: well-known/hallmark-cards-well-known.yml
- type: Plans
  url: plans/hallmark-cards-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hallmark-cards-rate-limits.yml
- type: FinOps
  url: finops/hallmark-cards-finops.yml
x-pointer-liveness:
  checked: '2026-09-17'
  method: curl with a browser User-Agent; title read from the body
  results:
  - url: https://www.hallmark.com
    status: 200
  - url: https://corporate.hallmark.com/
    status: 200
  - url: https://corporate.hallmark.com/hallmark-news/news/
    status: 200
  - url: https://corporate.hallmark.com/feed/
    status: 200
    content_type: application/rss+xml
  - url: https://ideas.hallmark.com/
    status: 200
  - url: https://ideas.hallmark.com/feed/
    status: 200
    content_type: application/rss+xml
  - url: https://care.hallmark.com/s/
    status: 200
  - url: https://careers.hallmark.com/
    status: 200
  - url: https://corporate.hallmark.com/business-opportunities/
    status: 200
  - url: https://corporate.hallmark.com/citizenship/hallmark-community/supplier-partnerships/
    status: 200
  - url: https://www.hallmarkbusiness.com/
    status: 200
  - url: https://www.hallmark.com/privacy/
    status: 200
  - url: https://www.hallmark.com/terms-of-use/
    status: 200
  - url: https://www.linkedin.com/company/hallmark-cards
    status: 200
  removed:
  - url: https://developer.hallmark.com
    status: 0
    note: DNS does not resolve; was humanURL of a fabricated API entry
  - url: https://developer.hallmark.com/docs
    status: 0
    note: DNS does not resolve; was the Documentation pointer of a fabricated API entry
  - url: https://api.hallmark.com
    status: 200
    note: resolves via Akamai but serves a stock ASP.NET MVC template; /Help, /openapi.json, /swagger.json, /api-docs, /docs,
      /graphql all 404 — not an API surface, removed as baseURL
x-evidence:
  verified: '2026-09-17'
  method: probed every host, searched the web, read the Business Connections and corporate sites
  summary: No API entry is listed because none could be evidenced. Web search for a Hallmark Cards developer API returns only
    unrelated projects (the Nxt blockchain "Hallmark" API, a third-party nondracek/hallmark-api scraper). The GitHub org HallmarkCards
    (Hallmark Cards UK) has 0 public repos and github.com/hallmark is an unrelated individual. Hallmark Business Connections
    markets CRM and SSO integrations for its B2B card programs but publishes no integration reference. Hallmark Global Services
    trades with retailers over EDI through TrueCommerce (a third-party network, 403 to our crawler). Hallmark is privately
    held, so there are no SEC EDGAR filings to list as a third-party government API.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-09-17'
  status: minimal
  artifacts_added: 1
  pass: local-v3
x-coverage:
  state: none
  reason: not-a-software-company
  detail: Hallmark sells physical greeting cards, gifts and ornaments plus television media; developer.hallmark.com does not
    resolve and api.hallmark.com is a stock ASP.NET template whose only link (/Help) 404s, with no spec, discovery document,
    agent card or llms.txt on any of five Hallmark hosts.
  evidence:
  - url: https://developer.hallmark.com/docs
    status: 0
  - url: https://api.hallmark.com/Help
    status: 404
  - url: https://api.hallmark.com/openapi.json
    status: 404
  - url: https://www.hallmark.com/.well-known/api-catalog
    status: 404
  - url: https://www.hallmark.com/llms.txt
    status: 404
  - url: https://www.hallmarkbusiness.com/developers/
    status: 404
  checked: '2026-09-17'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/hallmark-cards"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hallmark-cards/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hallmark-cards/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.