Add Apex Trading connector for wholesale cannabis platform

[Copilot]

Description

Implements TypeScript connector for Apex Trading wholesale cannabis platform API covering products, batches, orders, companies, and buyers resources.

Core implementation:

• Bearer token authentication with API key
• Offset-based pagination with configurable limits
• Incremental sync support using updated_at_from parameter
• Rate limiting at 15 req/sec per API specification
• Automatic retry with exponential backoff for 429/5xx responses

Resources:

• products - cannabis product catalog (list, get) with incremental sync
• batches - product batches with tracking and test results (list, get)
• orders - receiving, shipping, and transporter orders (list by type, get)
• companies - trading companies: distributors, retailers, manufacturers, cultivators (list, get)
• buyers - buyer information with purchase history (list, get)

Usage:

import { createConnector } from '@workspace/connector-apex-trading'

const connector = createConnector()
connector.initialize({
  apiKey: process.env.APEX_API_KEY!,
})

// Incremental sync for products
for await (const page of connector.products.list({ 
  updated_at_from: '2024-01-01T00:00:00Z',
  pageSize: 100 
})) {
  console.log(page)
}

// List receiving orders by status
for await (const page of connector.orders.receiving({ 
  status: 'confirmed' 
})) {
  console.log(page)
}

// Get company details
const company = await connector.companies.get('company-id')

Documentation:

• Comprehensive README for wholesale cannabis platform
• Configuration guide (auth, logging, metrics, rate limiting)
• API limits and best practices
• Example usage for inventory management and sales tracking

Testing Checklist

• Unit tests for all public methods
• Integration tests with mock servers
• Retry logic (backoff, jitter, circuit breaker)
• Rate limiting behavior
• Auth flows and expiry/refresh
• Error classification and propagation
• Pagination strategies and edge cases

Note

Initial implementation incorrectly targeted cryptocurrency trading APIs. Corrected to implement the actual Apex Trading wholesale cannabis platform API as documented at https://api-docs.apextrading.com/

• Fixes Connector Request #145

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Connector Request</issue_title>
<issue_description>Make a connector for all resources here: https://api-docs.apextrading.com/</issue_description>

Comments on the Issue (you are @copilot in this section)

Custom agent used: connector-implementer
Use this agent when the user is creating a new connector for the 514 Labs Registry, needs guidance on implementing connector resources, or is working on connector scaffolding, testing, or schema definition.

• Fixes Connector Request #145

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
registry	Error			Nov 11, 2025 8:57pm

[georgevanderson]

@copilot "our wholesale platform so I can get live snapshots of our current inventory and run Sales Performance reports. Some long term goals would be automated touch point reminders for the sales team based on different vendors velocity and their last purchase to remind them to help customer restock our product."
You hallucinated all these specs. Please explore the doucmentation at https://api-docs.apextrading.com/#7f121dc3-c937-4587-9c06-b8a1f3be53d0

[Copilot]

@copilot "our wholesale platform so I can get live snapshots of our current inventory and run Sales Performance reports. Some long term goals would be automated touch point reminders for the sales tea...

You're absolutely right - I apologize for the hallucination. I initially misidentified the Apex Trading API as a cryptocurrency exchange API when it's actually a wholesale cannabis trading platform.

I've corrected the implementation in commit f62139d to properly implement the actual API with resources for:

• Products (cannabis catalog with incremental sync)
• Batches (product tracking with test results)
• Orders (receiving/shipping/transporter)
• Companies (distributors, retailers, manufacturers, cultivators)
• Buyers (with purchase history)

The connector now correctly matches the API documented at https://api-docs.apextrading.com/