Skip to content

feat: add TypeScript SDK alongside Python SDK#11

Closed
saksham-nexla wants to merge 1 commit intomainfrom
refactor/remove-mcp-tools-toolsets-sessions
Closed

feat: add TypeScript SDK alongside Python SDK#11
saksham-nexla wants to merge 1 commit intomainfrom
refactor/remove-mcp-tools-toolsets-sessions

Conversation

@saksham-nexla
Copy link
Copy Markdown
Member

Summary

This PR introduces a new TypeScript SDK for Nexla, providing feature parity with the Python SDK for core operations. The TS SDK enables JavaScript/TypeScript developers to integrate Nexla into their applications seamlessly.

Key Features

  • NexlaClient with service key and access token authentication
  • Generated OpenAPI client from official Nexla OpenAPI spec
  • Type-safe resource clients for common operations (flows, sources, destinations, etc.)
  • Webhooks support for webhook signature verification and one-record sends
  • Comprehensive test coverage (unit tests with 90%+ coverage)
  • Automated CI/CD for testing, linting, and publishing

Test Coverage

  • Unit tests for all resource clients
  • Integration test infrastructure (non-blocking CI)
  • Coverage reporting enforced via CI checks

Documentation

  • Architecture overview
  • API parity matrix (Python ↔ TypeScript)
  • Migration guide from Python SDK
  • Integration testing policy

Monorepo Structure

  • packages/ts-sdk/ - TypeScript SDK source code
  • docs/ts-sdk/ - TypeScript-specific documentation
  • scripts/parity/ - Python/TS parity tooling

Checklist

  • All tests pass (unit + lint)
  • Documentation updated
  • Type checking enforced (no any types)
  • CI workflows configured

@saksham-nexla
Copy link
Copy Markdown
Member Author

Renaming branch - will open new PR with corrected branch name

@saksham-nexla saksham-nexla deleted the refactor/remove-mcp-tools-toolsets-sessions branch February 6, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant