lowes.com
Lowe’s is a home improvement retailer. Its developer-facing offerings support partner marketplace commerce flows, order and inventory integrations, and operational APIs for service providers managing jobs and related workflows.
Lowe’s exposes a public MCP server plus partner-focused B2B HTTP APIs for commerce and provider operations, authenticated primarily with OAuth 2.0 client credentials and, for LowesX commerce APIs, an additional X-Client-Id header.
- Lowe’s MCP Serverdiscovered
- Lowe's LowesX Commerce APIsdiscovered
Onboard through the Lowe's Developer Portal or contact the Lowe's partner integration team at DL-DIST-PLATFORM-LOWESX-TEAM-ALL@lowes.com to obtain environment-specific client_id and client_secret for the OAuth 2.0 client-credentials flow. Use the staging token endpoint POST https://apis-b2b-stage.lowes.com/v1/oauthprovider/oauth2/token for LowesX APIs, or the provider auth endpoint shown in PROvider Ops docs POST https://apis-b2b-stage.lowes.com/am/oauth2/realms/vendors/access_token with grant_type=client_credentials and your issued credentials. Staging and production credentials are separate.
Complete vendor onboarding via the Lowe's Developer Portal to receive your static X-Client-Id. Lowe's docs state this identifier is issued once during onboarding and is shared across Cart Connect, Purchase Connect, and Post-Purchase within an environment. Staging and production values are separate; contact DL-DIST-PLATFORM-LOWESX-TEAM-ALL@lowes.com if you have not yet onboarded.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing