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
  • Setup Access
  • Request an auth token
  • Add a facility
  • Next steps
Edit on GitHub
  1. Getting Started

Quickstart

Last updated 5 months ago

This tutorial will guide you through the initial setup required to make your first API call to fulfillmenttools.

Setup Access

  1. If you haven't already done so, request your free trial at to get started immediately!

  2. You will receive the following details:

    1. URL of your fulfillmenttools instance (a "tenant"). We refer to this value by using https://{YOUR_TENANT_NAME}.api.fulfillmenttools.com it throughout the documentation. Use this URL for requests to the REST API.

    2. URL to the fulfillmenttools Backoffice to use in your browser.

    3. Credentials for the project's initial admin user comprising username and password.

    4. A security-related API key (used for Authorization). Will be referred to as AUTHKEY in this documentation.

Request an auth token

Once your tenant is ready, you can request an auth token by sending the following request with your user credentials:

POST https://identitytoolkit.googleapis.com/v1/accounts:signInWithPassword?key={AUTHKEY}
{
  "email": {USERNAME},  
  "password": {PASSWORD}, 
  "returnSecureToken": true
}

If all credentials are successful, the endpoint will respond with a body similar to the following

{
  "kind": "identitytoolkit#VerifyPasswordResponse",
  "localId": "jdwBuqqYWdYoqWTH1Xv85EJJMpm2",
  "email": "willy@wonkacandycompany.com",
  "displayName": "Willy Wonka",
  "idToken": "eyJhbGciOiJSUzI1NiIsImtpZ...ynLgbiNgHJJxtBXSTSFnp2fA",
  "registered": true,
  "refreshToken": "AE0u-NeGDdHWPB0RjOYO...pRMKoncagBq30OFCJkEgpvyI",
  "expiresIn": "3600"
}

The idToken is your auth token for any future requests to the platform. Make sure to always include it as a header in each of your requests:

Authorization: Bearer {YOUR_ID_TOKEN}

Add a facility

Make sure to include the Content-Type: application/json header to all of your requests

You are now ready to make your first API Call. In this example, we will add a simple facility to your tenant:

POST https://{YOUR_TENANT_NAME}.api.fulfillmenttools.com/api/facilities
{
    "name": "Bills Candy Shop",
    "address": {
        "companyName": "Bills Candy Shop Ltd.",
        "country": "DE",
        "postalCode": "81669",
        "city": "München",
        "street": "Lilienstr.",
        "houseNumber": "58"
    },
    "services": [
    {
      "type": "SHIP_FROM_STORE"
    }
  ],
  "status": "ONLINE",
  "locationType": "STORE"
}

If successful, the endpoint will respond with 201 CREATED

{
    "name": "Bills Candy Shop",
    "address": {
        "companyName": "Bills Candy Shop Ltd.",
        "country": "DE",
        "postalCode": "81669",
        "city": "München",
        "street": "Lilienstr.",
        "houseNumber": "58"
    },
    "services": [
        {
            "type": "SHIP_FROM_STORE"
        }
    ],
    "status": "ONLINE",
    "locationType": "STORE",
    "fulfillmentProcessBuffer": 240,
    "capacityEnabled": false,
    "created": "2023-08-22T14:39:27.014Z",
    "lastModified": "2023-08-22T14:39:27.014Z",
    "version": 1,
    "id": "0dee02e8-f6a7-4080-b5ab-ffa477132f35"
}

The facility will now be visible in the backoffice, and you can use the facility ID to make all further requests.

Next steps

You are now equipped with the basic knowledge to make your first steps on our platform. If you're looking for a guided walkthrough to get to know fulfillmenttools better, we recommend checking out the Integration tutorial.

Additionally, the following resources will be helpful to learn more about our platform and available features:

  • Technical Basics

  • Core concepts

  • Postman

If you have any questions, please feel free to get in touch with us at !

https://fulfillmenttools.com/en/request-free-trial/
API Reference
professionalservice@fulfillmenttools.com