Burlington Stores
Burlington Stores, Inc. (NYSE: BURL) is a US national off-price department store retailer offering brand-name clothing, footwear, accessories, baby products and home decor at everyday low prices across more than 1,200 stores. Burlington operates no public developer program: no OpenAPI, GraphQL, gRPC, SOAP or event contract is served on any host it controls. Its one documented machine-to-machine surface is ASC X12 version 4010 EDI for merchandise vendors and freight carriers, and unusually for a retailer of this size the implementation guides are fully public — seventeen transaction-set PDFs plus a GS1-128 shipping label companion report, readable without a login at burlington.com/vendors/edi. The runtime behind them, the Gateway Vendor Management Suite, is invite-only.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Burlington Stores the way a machine reads it — 6 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Burlington Stores scores 10.4/100 (minimal), with a separate agent-readiness read of 5/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Burlington runs no developer program at all — every /.well-known/ path, /openapi.json and /llms.txt on www.burlington.com returns HTTP 200 carrying the site's Next.js shell titled '404 Not Found | Burlington' (a control path that cannot exist returns the same body), and vendors.burlington.com and edi.coat.com return honest 404s for all of them; the only documented machine-to-machine surface is ASC X12 4010 EDI, whose seventeen implementation guides ARE public at burlington.com/vendors/edi but which is batch interchange behind an invite-only Gateway login, not an API.
This is an honest zero, not a gap in our research. Burlington Stores does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.burlington.com/openapi.json→ HTTP 200https://www.burlington.com/zzz-definitely-not-a-page-12345→ HTTP 200https://vendors.burlington.com/.well-known/agent-card.json→ HTTP 404https://edi.coat.com/openapi.json→ HTTP 404https://www.burlington.com/vendors/edi→ HTTP 200https://cdn.sanity.io/files/k5c6l842/production/7e549f9134cb3625b47e650ef36dfadca0ca8ce3.pdf→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Burlington Stores's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/burlington-stores/"
title="Burlington Stores on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/burlington-stores.svg"
alt="Burlington Stores Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/burlington-stores/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/burlington-stores/"
title="Burlington Stores on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/burlington-stores/card.svg"
alt="Burlington Stores Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Burlington Stores
Each block below is one kind of artifact we hold for Burlington Stores. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Burlington Stores
Burlington's consumer storefront: shopping, store locator, gift cards, loyalty and credit card servicing. No public API is published behind it. Every /.well-known/ path, /openap...
Burlington Stores EDI
Burlington's ASC X12 version 4010 EDI trading-partner interface — the company's only documented machine-to-machine surface. Seventeen implementation guides are published as publ...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Burlington Stores Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Burlington Stores Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Burlington Stores — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/burlington-stores · machine-readable index on apis.io
This is an independent, third-party profile of Burlington Stores, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.