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
    • Inbound process
    • Outbound stocks
    • Purchase order
    • Receipt
    • Routing strategy (context-based multi-config DOMS)
    • 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
  • Create user
  • Modify user
  • Delete user
Edit on GitHub
  1. Integration Guides
  2. Basics

Users

Last updated 4 months ago

More Users-API information can be found here:

Note: The following calls are allowed for users with SUPERVISOR or ADMINISTRATOR role.

Create user

POST https://your.api.fulfillmenttools.com/api/users
{
    "firstname": "Donna",
    "lastname": "Sheridan-Carmichael",
    "username": "dsheridan",
    "password": "fsdf6556",
    "roles": [
        {
            "name": "FULFILLER",
            "facilities": [
                "0AMSoRCbm7kSM3LJPoeH"
            ]
        }
    ]
}

Response:
201 OK

After creating a user, we receive a 201 CREATED response:

{
    "id": "x5jrZrDHvYYs6HpaDICKYG4QuIk2"
    "username": "dsheridan",
    "firstname": "Donna",
    "lastname": "Sheridan-Carmichael",
    "customClaims": {
        "roles": [
            {
                "name": "FULFILLER",
                "facilities": [
                    "0T1vKaEar0nuG58CxzA5"
                ]
            }
        ]
    },
    "created": "2020-09-25T10:06:35.000Z",
    "lastModified": "2020-09-25T10:06:35.009Z",
    "version": 1
}

Modify user

Now we modify a user to set a new role in a facility.

PATCH https://your.api.fulfillmenttools.com/api/users/x5jrZrDHvYYs6HpaDICKYG4QuIk2
{
    "actions": [
        {
            "action": "ModifyUser",
            "roles": [
                {
                    "name": "SUPERVISOR",
                    "facilities": [
                        "0T1vKaEar0nuG58CxzA5"
                    ]
                }
            ]
        }
    ],
    "version": 1
}

After modifying a user, we receive a 200 OK response:

{
    "id": "x5jrZrDHvYYs6HpaDICKYG4QuIk2"
    "username": "dsheridan",
    "firstname": "Donna",
    "lastname": "Sheridan-Carmichael",
    "customClaims": {
        "roles": [
            {
                "name": "SUPERVISOR",
                "facilities": [
                    "0T1vKaEar0nuG58CxzA5"
                ]
            }
        ]
    },
    "created": "2020-09-25T10:06:35.000Z",
    "lastModified": "2030-10-01T09:12:22.000Z",
    "version": 2
}

Delete user

When a user is deleted, all currently active JWT Tokens of that user are invalidated.

DELETE https://your.api.fulfillmenttools.com/api/users/x5jrZrDHvYYs6HpaDICKYG4QuIk2
REST API documentation - Users