Fulfillment.com APIv2

api:fulfillment.com · v2.0 · source: apis.guru

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 simple concept to achieve this is outlined below. 1. Your application/script will ask you for your username and password , your client id and client secret will be accessible via a DB or ENV. 2. Request an access token + Your function should be capable of formatting your request for both a grant type of \"password\" (step 1) and \"refresh token

[![Connect-MCP](https://clawy.uk/mcp/badge/api%3Afulfillment.com.svg)](https://clawy.uk/mcp/s/api%3Afulfillment.com)