Automate Fulfillment.com APIv2
HumDay reads Fulfillment.com APIv2’s own published API description and derives 13 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Fulfillment.com APIv2 is
Welcome to our current iteration of our REST API. While we encourage you to upgrade to v2.0 we will continue support for our [SOAP API](https://github.com/fulfillment/soap-integration). # Versioning The Fulfillment.com (FDC) REST API is version controlled and backwards compatible. We have many future APIs scheduled for publication within our v2.0 spec so please be prepared for us to add data nodes
API host: api.fulfillment.com
What HumDay can do in Fulfillment.com APIv2
6 documented operations change something in Fulfillment.com APIv2.
- POSTNew Order
/orders - DELETECancel an Order
/orders/{id} - PUTShip an Order
/orders/{id}/ship - PUTUpdate Order Status
/orders/{id}/status - PUTInform us of an RMA
/returns - POSTGenerate an Access Token
/oauth/access_token
What HumDay can read from Fulfillment.com APIv2
These are the operations a schedule or a trigger can watch.
- GETList of Orders
/orders - GETList of Item Inventories
/inventory - GETList Order Accounting
/accounting - GETOrder Details
/orders/{id} - GETList Returns
/returns - GETAbout Me
/users/me - GETTracking
/track
How automating Fulfillment.com APIv2 works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Fulfillment.com APIv2 account.
- Grant access, then go live. You approve the specific Fulfillment.com APIv2 operations it may use — and only those.
Automate Fulfillment.com APIv2 with these
- Magento B2B455 operations
- Klaviyo345 operations
- Agco ATS AGCO277 operations
- BeezUP Merchant210 operations
- Rebilly184 operations
- reverb163 operations
- Jumpseller142 operations
- Swagger API2Cart141 operations
- Just Eat UK97 operations
- Billbee75 operations
- Velopayments Velo Payments75 operations
- Apigee Marketcheck71 operations
Categories
Questions about Fulfillment.com APIv2 automation
- Can HumDay connect to Fulfillment.com APIv2?
- Yes. HumDay reads Fulfillment.com APIv2's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 13 operations are documented.
- Do I need to write code to automate Fulfillment.com APIv2?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Fulfillment.com APIv2 account.
- What can HumDay do in Fulfillment.com APIv2?
- 6 of the 13 documented operations change something in Fulfillment.com APIv2, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Fulfillment.com APIv2 account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Fulfillment.com APIv2 is held behind that approval.
Where this came from
The operations above are read from a published API description for Fulfillment.com APIv2 at fulfillment.github.io/api/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.