Joor website screenshot

Joor

JOOR is a New York-based SaaS company (founded 2010) operating a leading B2B wholesale fashion commerce platform and digital marketplace that connects fashion brands with retailers to run their wholesale business end to end. The platform digitizes wholesale buying with online linesheets, lookbooks, virtual showrooms, order management, and the JOOR Marketplace, alongside products such as JOOR Pay (wholesale payments), JOOR Passport (virtual trade shows), and Retail data/analytics. JOOR connects thousands of brands with hundreds of thousands of retail doors globally. Its production platform is fronted by a Kong API gateway and secured with Keycloak-based OpenID Connect authentication; API access is partner/integration-oriented rather than a self-serve public developer program. This profile was enriched from JOOR's live public surface (OIDC discovery, GitHub organization, and status page).

Joor publishes 1 API on the APIs.io network. Tagged areas include Company, Fashion, Wholesale, Retail, and E-Commerce.

Joor’s developer surface includes authentication and 9 more developer resources.

🌐 Visit website 📡 Source on GitHub
16.0/100 emerging ▬ flat Agent 15/100 agent aware Full breakdown ↓
scored 2026-08-30 · rubric v0.17.2
AccessSelf serve
1 APIs
CompanyFashionWholesaleRetailE-CommerceB2BMarketplacePayments

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-30 · rubric v0.17.2
Composite quality — 16.0/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 2.0 / 17
Access Clarity 0.0 / 17
Operational Transparency 2.0 / 11
Contract Governance 1.9 / 10
Discoverability 6.5 / 9
Regulatory Posture 6.3 / 15
Agent readiness — 15/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 6 / 6
Agentic Commerce Surface 0 / 5
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.
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/. This rating is computed from github.com/api-evangelist/joor: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

JOOR Identity (OpenID Connect)

JOOR's production identity service, a Keycloak realm exposing standard OpenID Connect / OAuth 2.0 endpoints (authorize, token, userinfo, introspection, JWKS) used to authenticat...

Security Posture 2

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

Joor Authentication

openIdConnect/oauth2 · 1 scheme

SECURITY

Joor Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Joor Scopes

9 scopes · authorizationCode/clientCredentials

9 scopes

SCOPES

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown
WellKnown
 LLMsTxt
LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 Lifecycle
Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication
 OAuthScopes
OAuthScopes

Operate 1

Status, limits, changes, and where to get help

StatusPage
StatusPage

Company 1

The organization behind the API

Website
Website

Source (apis.yml)

apis.yml Raw ↑ 
aid: joor
name: Joor
description: JOOR is a New York-based SaaS company (founded 2010) operating a leading B2B wholesale fashion commerce platform
  and digital marketplace that connects fashion brands with retailers to run their wholesale business end to end. The platform
  digitizes wholesale buying with online linesheets, lookbooks, virtual showrooms, order management, and the JOOR Marketplace,
  alongside products such as JOOR Pay (wholesale payments), JOOR Passport (virtual trade shows), and Retail data/analytics.
  JOOR connects thousands of brands with hundreds of thousands of retail doors globally. Its production platform is fronted
  by a Kong API gateway and secured with Keycloak-based OpenID Connect authentication; API access is partner/integration-oriented
  rather than a self-serve public developer program. This profile was enriched from JOOR's live public surface (OIDC discovery,
  GitHub organization, and status page).
url: https://raw.githubusercontent.com/api-evangelist/joor/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
- canaan-partners
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.jooraccess.com/favicon.ico
tags:
- Company
- Fashion
- Wholesale
- Retail
- E-Commerce
- B2B
- Marketplace
- Payments
tags_raw:
- Company
- Fashion
- Wholesale
- Retail
- eCommerce
- B2B
- Marketplace
- Payments
apis:
- name: JOOR Identity (OpenID Connect)
  description: JOOR's production identity service, a Keycloak realm exposing standard OpenID Connect / OAuth 2.0 endpoints
    (authorize, token, userinfo, introspection, JWKS) used to authenticate access to the JOOR platform and its partner/integration
    APIs behind the Kong gateway.
  humanURL: https://auth.jooraccess.com/auth/realms/joor/.well-known/openid-configuration
  baseURL: https://auth.jooraccess.com/auth/realms/joor
  properties:
  - type: OpenIDConnect
    url: https://auth.jooraccess.com/auth/realms/joor/.well-known/openid-configuration
  - type: Authentication
    url: authentication/joor-authentication.yml
  - type: OAuthScopes
    url: scopes/joor-scopes.yml
common:
- type: DomainSecurity
  url: security/joor-domain-security.yml
- type: Website
  url: https://www.jooraccess.com
- type: GitHubOrganization
  url: https://github.com/joor
- type: StatusPage
  url: https://status.joor.com
- type: WellKnown
  url: well-known/joor-well-known.yml
- type: Authentication
  url: authentication/joor-authentication.yml
- type: OAuthScopes
  url: scopes/joor-scopes.yml
- type: Conformance
  url: conformance/joor-conformance.yml
- type: Lifecycle
  url: lifecycle/joor-lifecycle.yml
- type: LLMsTxt
  url: llms/joor-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/joor"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/joor/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/joor/evidence"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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