fulfillmenttools
API documentationIncident ManagementFeedback
Developer Docs
Developer Docs
  • Developer docs
  • Getting Started
    • Quickstart
    • Integration tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
    • Free trial
  • Technical Basics
    • Access to fulfillmenttools
    • Feature status
    • Available regions
    • Backup policies
  • Connecting to fulfillmenttools
    • Client SDKs
    • commercetools connect
    • OpenID connect
      • Configure Microsoft Entra ID / Azure Active Directory
      • Configure Keycloak
  • API
    • Core concepts
      • Authentication & authorization
      • API Versioning & lifecycle
      • Assign user to jobs
      • Localization
      • Resource timestamps
      • Custom attributes
      • Article attributes
      • Recordable attributes
      • Data update guarantees
      • Rate limits & scaling
      • Retries
      • Performance on test vs. production systems
      • Load testing
    • API calls
      • Postman
      • cURL
      • GraphQL Explorer
    • GraphQL API
    • RESTful API
      • Pagination interface
      • RapiDoc
      • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an event
      • Available events
        • Event flows
      • Eventing example
      • Event export
  • Integration Guides
    • Basics
      • Article categories
      • Audits
      • Facilities
      • Facility groups
      • GDPR configuration
      • Listings
      • Remote configuration
      • Receipts
      • Search
      • Subscribe to events
      • Sticker
      • Stocks
      • Storage locations
      • Tags
      • Users
    • Channel inventory
    • Facility discounts
    • Inbound process
    • Outbound stocks
    • Purchase order
    • Receipt
    • Routing strategy
    • Show sticker to clients
    • Stow jobs
  • More Integration Guides
    • Carrier management
      • Introduction to carrier configuration
      • Required data when operating carriers
      • Adding & connecting carriers to facilities
      • Custom carrier
    • Configurations for order fulfillment
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing and document configuration
      • Packing container types
      • Parcel tag configuration
      • Headless order fulfillment
      • Short-pick reasons
      • External documents in order fulfillment
      • Service jobs
      • Load units
      • Running sequence
    • DOMS - distributed order management system (routing)
    • External actions
    • Interfacility transfer
    • Notifications
    • Orders
      • Place your first order
      • Ship-from-store orders
      • Click-and-collect orders
      • Locked orders
      • Order with custom services
      • Bundled items in an order
      • Order process status
    • Availability & promising
    • Returns
Powered by GitBook
On this page
  • fulfillmenttools SDK
  • Generating a client
  • TypeScript example
Edit on GitHub
  1. Connecting to fulfillmenttools

Client SDKs

Last updated 5 months ago

We provide an official client SDK for the fulfillmenttools platform (which is in beta status), and you can generate a client using third-party tools.

fulfillmenttools SDK

The official fulfillmenttools client SDK in TypeScript is now available on and and can be used wherever you run JavaScript.

The TypeScript SDK is open source and licensed under the MIT License. This means that you can use it in your projects and contribute to its development.

Learn how to set up and use the TypeScript SDK with our .

Currently, this client SDK does not provide access to all of our API's features, but we are continuously extending it and pushing out new versions. We hope you will find it easy to use and are looking forward to your feedback.

Generating a client

Another approach is to use , which can generate client SDKs from an OpenAPI specification for a wide range of programming languages.

Of course, you can also use other tools (e.g. ) or choose not to generate classes/types and manually model the pieces you need for your particular use case.

The Swagger has more details on this tool.

TypeScript example

Here's an example of how to generate a TypeScript client:

  1. Follow the on GitHub.

  2. Download our fulfillmenttools OpenAPI specification .

  3. Use the Swagger Codegen CLI tool to generate a TypeScript client:

java -jar swagger-codegen-cli-3.0.62.jar generate \
  -i api.swagger.yaml \
  -l typescript-fetch \
  -o client
  1. This will put the generated classes into the client folder. In this folder, the api.ts file contains the generated namespaces, interfaces, etc. and is especially interesting for us.

  2. Depending on your preferences, you can use all the generated client classes or only pick up the generated enum, interface, namespace, type and implement the actual client yourself.

GitHub
npm
tutorial on GitHub
Swagger Codegen
OpenAPI Generator
Codegen GitHub repository
Swagger Codegen CLI Tool instructions
api.swagger.yaml