API archive entry · source-reported
Fulfillment.com APIv2
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. # 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 in our responses, however, we will not remove knowledge from previously published APIs. #### A Current Response ```javascript { id: 123 } ``` #### A Potential Future Response ```javascript { id: 123, reason: "More Knowledge" } ``` # Getting Started We use OAuth v2.0 to authenticate clients, you can choose implicit or password grant type. To obtain an OAuth `client_id` and `client_secret` contact your account executive. **Tip**: Generate an additional login and use those credentials for your integration so that changes are accredited to that "user". You are now ready to make requests to our other APIs by filling your `Authorization` header with `Bearer {access_token}`. ## Perpetuating Access Perpetuating access to FDC without storing your password locally can be achieved using the `refresh_token` returned by POST /oauth/access_token. A sim
Archive history
This history reflects directory observations and owner review, not a provider release log.
- First observed: Sep 20, 2026
- Last directory-field change: Sep 20, 2026
- Current source observation: Sep 20, 2026
Published source events
added
Sep 20, 2026 · Added from an approved API directory.
Where to check product changes
Use the provider documentation and status channels for releases, breaking changes, and outages.
Source reference
This page separates source-reported facts from questions that need live provider verification.