• Push RFQs

    • Show/Hide
    • List Operations
    • Expand Operations

      • POST PushRfq

        • Automatically sends the seller's pending RFQs to the endpoint configured in the database for that seller, running every 3 minutes.

        Implementation Notes

        Designed for sellers. This is a background process (not an on-demand API call) that automatically pushes pending RFQs (status = 1, not sent) to the seller's configured endpoint. The seller's destination URL and credentials are stored in the database and must be configured manually. Supports JSON and XML formats based on the seller's configuration. Includes retry logic and error notification via email when delivery fails.

        Example Request Body

        {
    "RfqId": 0,
    "Guid": "string",
    "RfqDate": "yyyy-MM-ddTHH:mm:ss EST",
    "ResponsesDueBy": "yyyy-MM-ddTHH:mm:ss EST",
    "TrackNum": "string",
    "BuyerId": 0,
    "BuyerCompany": "string",
    "BuyerAddress": "string",
    "BuyerAddress2": "string",
    "BuyerCity": "string",
    "BuyerState": "string",
    "BuyerZip": "string",
    "BuyerCountry": "string",
    "BuyerName": "string",
    "BuyerPhone": "string",
    "BuyerFax": "string",
    "BuyerEmail": "string",
    "SellerCompany": "string",
    "SellerUserName": "string",
    "SellerName": "string",
    "SellerPhone": "string",
    "SellerEmail": "string",
    "RfqLineItems": [{
        "RfqItemBidId": 0,
        "PartNumber": "string",
        "AltPartNumber": "string",
        "PartDescription": "string",
        "ConditionCode": "string",
        "Quantity": 0,
        "ReqDeliveryDays": 0,
        "Comments": "string",
        "RfqItemId": 0,
        "IsOverhaul": false,
        "SenderInvQuantity": 0,
        "SenderListingInv": 0,
        "SupplierPartNumber": 0,
        "SupplierQuantity": 0
    }]
}
        <?xml version="1.0" ?>
<Rfq>
    <RfqId>0</RfqId>
    <Guid>string</Guid>
    <RfqDate>yyyy-MM-ddTHH:mm:ss EST</RfqDate>
    <ResponsesDueBy>yyyy-MM-ddTHH:mm:ss EST</ResponsesDueBy>
    <TrackNum />
    <BuyerId>0</BuyerId>
    <BuyerCompany>string</BuyerCompany>
    <BuyerAddress>strings</BuyerAddress>
    <BuyerAddress2 />
    <BuyerCity>string</BuyerCity>
    <BuyerState>string</BuyerState>
    <BuyerZip>0</BuyerZip>
    <BuyerCountry>string</BuyerCountry>
    <BuyerName>string</BuyerName>
    <BuyerPhone>string</BuyerPhone>
    <BuyerFax />
    <BuyerEmail>string</BuyerEmail>
    <SellerCompany>string</SellerCompany>
    <SellerUserName>string</SellerUserName>
    <SellerName>string</SellerName>
    <SellerPhone>string</SellerPhone>
    <SellerEmail>string</SellerEmail>
    <RfqLineItems>
        <RfqLineItem>
            <RfqItemBidId>0</RfqItemBidId>
            <PartNumber>string</PartNumber>
            <AltPartNumber />
            <PartDescription>string</PartDescription>
            <ConditionCode>string</ConditionCode>
            <Quantity>0</Quantity>
            <ReqDeliveryDays>0</ReqDeliveryDays>
            <Comments />
            <RfqItemId/>
            <IsOverhaul/>
            <SenderInvQuantity/>
            <SenderListingInv/>
            <SupplierPartNumber/>
            <SupplierQuantity/>
        </RfqLineItem>
    </RfqLineItems>
</Rfq>

        See Description Model

        Response Class (Status 200)

        Successful Request

        • Model
        • Example Value
        {
    respCode : 0
    respMessage : "string"
}
        
<?xml version="1.0"?>
<PartsBaseResponse>
    <respCode>0</respCode>
    <respMessage>string</respMessage>
</PartsBaseResponse>
        [XmlRoot("PartsBaseResponse")]
        PartsBaseResponse {
        [XmlElement("respCode")]
        respCode (integer, optional): A boolean if an error occurred while processing request.
        [XmlElement("respMessage")]
        respMessage (string, optional): Description message for error.
        }


        Response Messages

        HTTP Status Code Reason Response Model Headers
        401

        Unauthorized
        string
        500

        InternalServerError
        string

  • Response RFQs

    • Show/Hide
    • List Operations
    • Expand Operations

      • POST PushRfqResponse

        • Sends RFQs that have already been answered (quotes generated) to the seller's configured endpoint, as part of the Push RFQ background process.

        Implementation Notes

        Designed for sellers. Similar to Push RFQ, but this process only delivers RFQs that have already been responded to by the seller (status = 3, sent; UnitPrice IS NOT NULL). It runs alongside Push RFQ in the same background worker and pushes the quoted RFQ data to the seller's configured endpoint. This allows the seller's external system to receive confirmation of the quotes they have submitted.

        Example Request Body

        
    {
    "RfqId": 0,
    "Guid": "string",
    "RfqDate": "yyyy-MM-ddTHH:mm:ss EST",
    "ResponsesDueBy": "yyyy-MM-ddTHH:mm:ss EST",
    "TrackNum": "string",
    "BuyerId": 0,
    "BuyerCompany": "string",
    "BuyerAddress": "string",
    "BuyerAddress2": "string",
    "BuyerCity": "string",
    "BuyerState": "string",
    "BuyerZip": "string",
    "BuyerCountry": "string",
    "BuyerName": "string",
    "BuyerPhone": "string",
    "BuyerFax": "string",
    "BuyerEmail": "string",
    "SellerCompany": "string",
    "SellerUserName": "string",
    "SellerName": "string",
    "SellerPhone": "string",
    "SellerEmail": "string",
    "RfqLineItems": [{
    "RfqItemBidId": 0,
    "PartNumber": "string",
    "AltPartNumber": "string",
    "PartDescription": "string",
    "ConditionCode": "string",
    "Quantity": 0,
    "ReqDeliveryDays": 0,
    "Comments": "string",
    "RfqItemId": 0,
    "IsOverhaul": false,
    "SenderInvQuantity": 0,
    "SenderListingInv": 0,
    "SupplierPartNumber": 0,
    "SupplierQuantity": 0,
    "PriceType": "string",
    "Traceability": "string",
    "QuantityAv": 0,
    "UoM": "string",
    "UnitPrice": 0.0
    }]
    }

        
    <?xml version="1.0" ?>
    <Rfq>
    <RfqId>0</RfqId>
    <Guid>string</Guid>
    <RfqDate>yyyy-MM-ddTHH:mm:ss EST</RfqDate>
    <ResponsesDueBy>yyyy-MM-ddTHH:mm:ss EST</ResponsesDueBy>
    <TrackNum />
    <BuyerId>0</BuyerId>
    <BuyerCompany>string</BuyerCompany>
    <BuyerAddress>strings</BuyerAddress>
    <BuyerAddress2 />
    <BuyerCity>string</BuyerCity>
    <BuyerState>string</BuyerState>
    <BuyerZip>0</BuyerZip>
    <BuyerCountry>string</BuyerCountry>
    <BuyerName>string</BuyerName>
    <BuyerPhone>string</BuyerPhone>
    <BuyerFax />
    <BuyerEmail>string</BuyerEmail>
    <SellerCompany>string</SellerCompany>
    <SellerUserName>string</SellerUserName>
    <SellerName>string</SellerName>
    <SellerPhone>string</SellerPhone>
    <SellerEmail>string</SellerEmail>
    <RfqLineItems>
    <RfqLineItem>
    <RfqItemBidId>0</RfqItemBidId>
    <PartNumber>string</PartNumber>
    <AltPartNumber />
    <PartDescription>string</PartDescription>
    <ConditionCode>string</ConditionCode>
    <Quantity>0</Quantity>
    <ReqDeliveryDays>0</ReqDeliveryDays>
    <Comments />
    <RfqItemId/>
    <IsOverhaul/>
    <SenderInvQuantity/>
    <SenderListingInv/>
    <SupplierPartNumber/>
    <SupplierQuantity/>
    <PriceType/>
    <Traceability/>
    <QuantityAv/>
    <UoM/>
    <UnitPrice/>
    </RespRfqLineItem>
    </RfqLineItems>
    </Rfq>

        See Description Model

        Response Class (Status 200)

        Successful Request

        • Model
        • Example Value
        {
    respCode : 0
    respMessage : "string"
}
        
<?xml version="1.0"?>
<PartsBaseResponse>
    <respCode>0</respCode>
    <respMessage>string</respMessage>
</PartsBaseResponse>
        [XmlRoot("PartsBaseResponse")]
        PartsBaseResponse {
        [XmlElement("respCode")]
        respCode (integer, optional): A boolean if an error occurred while processing request.
        [XmlElement("respMessage")]
        respMessage (string, optional): Description message for error.
        }


        Response Messages

        HTTP Status Code Reason Response Model Headers
        401

        Unauthorized
        string
        500

        InternalServerError
        string

  • Send RFQs

    • Show/Hide
    • List Operations
    • Expand Operations

      • GET /api-sendrfq

        • Retrieves the status of an RFQ and its associated items by RFQ identifier.

        Implementation Notes

        Designed for buyers. Retrieves the current status of a previously submitted RFQ and the status of each individual RFQ item. The buyer must first obtain an access token, then use this GET endpoint with the RFQ identifier to check the progress of the request.

        *Note: This service uses the base URL: https://services.partsbase.com, please consider it in your implementation.

        Example

        GET https://services.partsbase.com/api-sendrfq?rfqId=7923453 HTTP/1.1

        Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImEzck1VZ01Gdjl0

        Accept: application/json


        Response Class (Status 200)

        Successful Request

        • Model
        • Example Value
        
    {
    "RFQItemId": 0,
    "Status": "string",
    "Items":[
        {
            'RFQItemId': 0,
            'Status': 'string'
        },
        {
            'RFQItemId': 0,
            'Status': 'string'
        }
      ]
    }
        MarketsPricingViewModel {
        ValuesPerCode (Array[MarketPricingItemModel], optional): Array of items where every item represents a Market Pricing per Condition Code. ,
        PartNumber (string, optional): Part number
        }
        MarketPricingItemModel {
        ConditionCode (string, optional): Buyer requested Part Number’s Condition Code See Condition Codes Catalog.
        LastUpdated (string, optional): Last updated in Number Part per Condition Code
        MaxUnitPrice (number, optional): Maximum of unit price by Number Part
        MinUnitPrice (number, optional): Minimum of unit price by Number Part
        }


        Parameters

        Parameter Value Description Parameter Type Data Type
        (empty) RFQ Identififier. This parameter is mandatory path string

        Response Messages

        HTTP Status Code Reason Response Model Headers
        400

        Bad request
        • Model
        • Example Value
        Error {
        Error (string, optional): Description message for error.
        } 
        {
    "message": "string",
}
        401

        Unauthorized
        string
        404

        Not Found
        string
        500

        InternalServerError
        string

      • POST /api-sendrfq

        • Allows a buyer to build and submit an RFQ (Request for Quote) for parts and capabilities to one or more sellers.

        Implementation Notes

        Designed for buyers. Allows the buyer to build and submit an RFQ to one or more sellers in the PartsBase system. A prior Real Time Search must be performed to obtain the Inventory ID of the items to be included. Returns the RFQ identifier and a list of any parts that were considered as not qualified.

        *Note:

        -This service uses the base URL: https://services.partsbase.com, please consider it in your implementation.

        -Duplicated Inventory IDs per RFQ will be ignored.

        -The Inventory ID is obtained from the Real Time Search endpoint response.

        Example

        POST https://services.partsbase.com/api-sendrfq HTTP/1.1

        Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImEzck1VZ01Gdjl0

        Accept: application/json

        Example Request Body


        
    {
    "Parts":[
        {
            "InventoryId" : integer,
            "Quantity": integer,
            "UoM": string
        },
        {
            "InventoryId" : integer,
            "Quantity": integer,
            "UoM": string
        },
      ],
    "ResponseByDate": string,
    "LeadTime": integer,
    "RFQTrackingNo": string,
    "Comments": string,
    "MRO": boolean
    }

        See Description Model

        Response Class (Status 200)

        Successful Request

        • Model
        • Example Value
        
    {
    "rfqId": 0,
    "rfqNotQualifiedList": []
    }


        Response Messages

        HTTP Status Code Reason Response Model Headers
        400

        Bad request
        • Model
        • Example Value
        Error {
        Error (string, optional): Description message for error.
        } 
        {
    "message": "string",
}
        401

        Unauthorized
        string
        404

        Not Found
        string
        500

        InternalServerError
        string

  • Parts Market Pricing

    • Show/Hide
    • List Operations
    • Expand Operations

      • GET /prod-pbd-marketpricing?partnumber={partNumber}

        • This service returns the market pricing information for one part number in the PartsBase system.

        Implementation Notes

        Service consumer does a request to get an access token. With that token, service consumer does a request to the GET MarketPricing operation and gets the market pricing per condition code related with a part number.

        Example

        GET https://services.partsbase.com/prod-pbd-marketpricing?partnumber=dk120 HTTP/1.1

        Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImEzck1VZ01Gdjl0

        Accept: application/json


        Response Class (Status 200)

        Successful Request

        • Model
        • Example Value
        
    {
    "valuesPerCode": [
    {
    "conditionCode": "string",
    "lastUpdated": "yyyy-MM-ddTHH:mm:ss EST",
    "maxUnitPrice": "0",
    "medianUnitPrice": "0",
    "minUnitPrice": "0",
    "partNumber": "string"
    }
    ]
    }
        MarketsPricingViewModel {
        ValuesPerCode (Array[MarketPricingItemModel], optional): Array of items where every item represents a Market Pricing per Condition Code. ,
        PartNumber (string, optional): Part number
        }
        MarketPricingItemModel {
        ConditionCode (string, optional): Buyer requested Part Number’s Condition Code See Condition Codes Catalog.
        LastUpdated (string, optional): Last updated in Number Part per Condition Code
        MaxUnitPrice (number, optional): Maximum of unit price by Number Part
        MinUnitPrice (number, optional): Minimum of unit price by Number Part
        }


        Response Messages

        HTTP Status Code Reason Response Model Headers
        401

        Unauthorized
        string
        500

        InternalServerError
        string
  • Additional Content

  • Appendix A

    • Show/Hide
      • Inventory Import Stock Configuration

        The process for Upload Inventory can be performed in different ways according to user configuration set up in database

        • Delimiter. The data file is composed by columns where every column is delimited by a special character. The characters allowed as delimiters are:
          • TAB. When the file is created, the TAB character is represented in a string as “\t”.
          • COMMA. Use the character “,” to delimiter.
          • SEMICOLON. Use the character “;” as delimiter.
        • Fixed Width Field. Indicates that data file columns don’t are delimited by any character. Working with this configuration, every column must define its own length.
        • With Quotes. Indicates if the columns content is between quotes, quotes will be removed from the file. This feature can be used with Delimiter only.
        • Header. Represents the total of rows used as header in the data file to be processed. Zero (0) in case of no header. This feature can be used with Fixed Width Field only.


        Inventory Import Stock Data File Validations

        Some validations to consider in the process for Inventory Import Stocks are:

        • As performance validation, be sure that the first record is correct else the file will be processed manually.
        • If a file has less of 100 records, all valid records will be processed.
        • If the total of records is equal or greater than 100 the file will be processed automatically if the invalid rows number is less than LIMIT else the file be kept in queue waiting for operation support team process it manually; LIMIT = integerPercent * 10 where integerPercent = (int)(Total Records/100)
        • Parts will be considering as equal than others if the fields PARTNUMBER and CONDITIONCODE are the same between them.
        • An Alternate Part Number is set to null when has a white space.

        Inventory Import Stock Files Examples.

        • Delimiter by Semicolon and Action Code Replacement (R).

          Manifest File Example 
          <?xml version="1.0" encoding="unicode" ?>
<FIELDS>
    <FIELD NAME="ACTION_CODE" TYPE="CHAR" LENGTH="1" />
    <FIELD NAME="PARTNUMBER" TYPE="CHAR" />
    <FIELD NAME="DESCRIPTION" TYPE="CHAR" />
    <FIELD NAME="ALTERNATEPARTNUMBER" TYPE="CHAR" />
    <FIELD NAME="CONDITIONCODE" TYPE="CHAR" />
    <FIELD NAME="QUANTITY" TYPE="INTEGER" />
    <FIELD NAME="UOM" TYPE="CHAR" />
    <FIELD NAME="MANUFACTURER" TYPE="CHAR" />
    <FIELD NAME="UNITPRICE" TYPE="DECIMAL" />
</FIELDS>
          Data File Example

          R;222-12222;TEST DESCR;99160-1988;NE;20;EA;SPACE X MANUFAC;200.00

          R;111-211111;NEW DESCRIPTION;78942-1245;NE;01;EA;MY MANUFACTURER;010.00

        • Delimiter by Semicolon, Action Code Replacement (R) and with Quotes

          Manifest File Example 
          <?xml version="1.0" encoding="unicode" ?>
<FIELDS>
    <FIELD NAME="ACTION_CODE" TYPE="CHAR" LENGTH="1" />
    <FIELD NAME="PARTNUMBER" TYPE="CHAR" />
    <FIELD NAME="DESCRIPTION" TYPE="CHAR" />
    <FIELD NAME="ALTERNATEPARTNUMBER" TYPE="CHAR" />
    <FIELD NAME="CONDITIONCODE" TYPE="CHAR" />
    <FIELD NAME="QUANTITY" TYPE="INTEGER" />
    <FIELD NAME="UOM" TYPE="CHAR" />
    <FIELD NAME="MANUFACTURER" TYPE="CHAR" />
    <FIELD NAME="UNITPRICE" TYPE="DECIMAL" />
</FIELDS>
          Data File Example

          R;"222-12222";"TEST DESCR";"99160-1988";"NE";"20";"EA";"SPACE X MANUFAC";"200.00"

          R;"111-211111";"NEW DESCRIPTION";"78942-1245";"NE";"01";"EA";"MY MANUFACTURER";"010.00"

        • Fixed Width Field and Action Code Replacement (R).

          Manifest File Example 
          <?xml version="1.0" encoding="unicode" ?>
<FIELDS>
    <FIELD NAME="ACTION_CODE" TYPE="CHAR" LENGTH="1" />
    <FIELD NAME="PARTNUMBER" TYPE="CHAR" LENGTH="10" />
    <FIELD NAME="DESCRIPTION" TYPE="CHAR" LENGTH="15" />
    <FIELD NAME="ALTERNATEPARTNUMBER" TYPE="CHAR" LENGTH="10" />
    <FIELD NAME="CONDITIONCODE" TYPE="CHAR" LENGTH="2" />
    <FIELD NAME="QUANTITY" TYPE="INTEGER" LENGTH="2" />
    <FIELD NAME="UOM" TYPE="CHAR" LENGTH="2" />
    <FIELD NAME="MANUFACTURER" TYPE="CHAR" LENGTH="15" />
    <FIELD NAME="UNITPRICE" TYPE="DECIMAL" LENGTH="5" />
</FIELDS>
          Data File Example

          R222-1222   TEST DESCR         99160-1988NE20EASPACE  X  MANUFAC200.00

          R111-211111NEW DESCRIPTION78942-1245NE01EAMY MANUFACTURER010.00

        • Fixed Width Field, Action Code Replacement (R) and one row as Header.

          Manifest File Example 
          <?xml version="1.0" encoding="unicode" ?>
<FIELDS>
    <FIELD NAME="ACTION_CODE" TYPE="CHAR" LENGTH="1" />
    <FIELD NAME="PARTNUMBER" TYPE="CHAR" LENGTH="10" />
    <FIELD NAME="DESCRIPTION" TYPE="CHAR" LENGTH="15" />
    <FIELD NAME="ALTERNATEPARTNUMBER" TYPE="CHAR" LENGTH="10" />
    <FIELD NAME="CONDITIONCODE" TYPE="CHAR" LENGTH="2" />
    <FIELD NAME="QUANTITY" TYPE="INTEGER" LENGTH="2" />
    <FIELD NAME="UOM" TYPE="CHAR" LENGTH="2" />
    <FIELD NAME="MANUFACTURER" TYPE="CHAR" LENGTH="15" />
    <FIELD NAME="UNITPRICE" TYPE="DECIMAL" LENGTH="5" />
</FIELDS>
          Data File Example
          RPARTNUMBERDESCRIPTION ALTERNATEPCCQUUOMANUFACTURER UNITPR

          R222-1222   TEST DESCR         99160-1988NE20EASPACE  X  MANUFAC200.00

          R111-211111NEW DESCRIPTION78942-1245NE01EAMY MANUFACTURER010.00

        • Fixed Width Field, Action Code Replacement (R) and two rows as Header.

          Manifest File Example 
          <?xml version="1.0" encoding="unicode" ?>
<FIELDS>
    <FIELD NAME="ACTION_CODE" TYPE="CHAR" LENGTH="1" />
    <FIELD NAME="PARTNUMBER" TYPE="CHAR" LENGTH="10" />
    <FIELD NAME="DESCRIPTION" TYPE="CHAR" LENGTH="15" />
    <FIELD NAME="ALTERNATEPARTNUMBER" TYPE="CHAR" LENGTH="10" />
    <FIELD NAME="CONDITIONCODE" TYPE="CHAR" LENGTH="2" />
    <FIELD NAME="QUANTITY" TYPE="INTEGER" LENGTH="2" />
    <FIELD NAME="UOM" TYPE="CHAR" LENGTH="2" />
    <FIELD NAME="MANUFACTURER" TYPE="CHAR" LENGTH="15" />
    <FIELD NAME="UNITPRICE" TYPE="DECIMAL" LENGTH="5" />
</FIELDS>
          Data File Example
          R           DATA FILE

          RPARTNUMBERDESCRIPTION ALTERNATEPCCQUUOMANUFACTURER UNITPR

          R222-1222   TEST DESCR         99160-1988NE20EASPACE  X  MANUFAC200.00

          R111-211111NEW DESCRIPTION78942-1245NE01EAMY MANUFACTURER010.00

  • Authentication Service

    • Show/Hide
    • List Operations
    • Expand Operations

      • POST /connect/token

        • Service for authenticating a system entity and authorize the use of web API methods.

        Implementation Notes



        Example Request Body

        The Authorization Service exposes only one operation: Token. This operation receives the service consumer’s credentials and returns an access token for valid credentials else an invalid grant message is returned


        Example
        POST https://auth.partsbase.com/connect/token HTTP/1.1

        Content-Type: application/x-www-form-urlencoded

        Request Body: grant_type=password&client_id=TestClientId&client_secret=0F8F-D9CB-469F7086&scope=api&username=TestUserName&password=TestPassword

        See Request body Description

        Response Class (Status 200)

        Successful Request

        • Model
        • Example Value
        {
    "access_token": "string",
    "expires_in": 0,
    "token_type": "string"
}
        Identity {
        access_token (String, optional): Access token to be used in the PartsBase API suite request.
        expires_in (Int, optional): Expiration time in seconds for the access token received.
        token_type (String, optional): Kind of token to be used in the authorization header for next requests.
        }


        Response Messages

        HTTP Status Code Reason Response Model Headers
        400

        Bad Request
        • Model
        • Example Value
        Error {
        Error (string, optional): Description message for error.
        } 
        {
    "error": "string",
}
        500

        InternalServerError
        string

  • Revision Record

    • Show/Hide

      • Revision Letter

        Description

        Revision Date

        Entered By

        A

        - Editorial changes to bring document into a new format

        October 11, 2017

        Francisco Lara
        B

        - New Stage environment servers.


        - Inventory Export Stocks. Part number as mandatory field and description field as optional.


        - Real Time Search service. Quantity field change from Integer to String.


        - Send Quote service information with Appendix C.

        January 24, 2018

        Francisco Lara

        C

        - GovData Service

        April 23, 2018

        Francisco Lara

        D

        - Pull Rfq Service updated to Version 2

        May 3, 2018

        Karla Ortiz

        E

        - New fields in RealTime search

        June 4, 2018

        Dario Almeida

        F

        - Post Online Document

        September 27, 2018

        Roberto Valdez

        G

        - Quote Service

        September 27, 2018

        Dario Almeida

        H

        - Market Pricing Service


        - MRO Market Pricing Service

        September 27, 2018

        Jesse Madriz

        I

        - Send RFQs

        February 29, 2024

        Eric Rodriguez

        J

        - FAQs

        December 5, 2024

        Eric Rodriguez

        K

        - Pull RFQs. Sort descending and allow optional fields to be empty


        - Parts Real Time Search. Allow optional fields to be empty


        - Send RFQs. Allow optional fields to be empty

        March 07, 2025

        Eric Rodriguez

  • FAQs

    • How do I obtain PartsBase API Credentials?

      Please reach out to your PartsBase account manager to formally request the credentials or send an Email to service@partsbase.com

    • What integration partners can I use to consume PartsBase API services?

      You can review all of our current integration partners here: Integration Partners page

    • Do authentication service tokens expire?

      Yes, when an authentication token is returned it will expire 5000 seconds after being provided.

    • When consuming the authentication service, I receive an "Invalid username or password" error, why?

      Our API credential’s username value is directly related to your PartsBase administrator user, you may have updated your password in PartsBase and not changed the password value when consuming the authentication service. Please update the password value to be the same password as your PartsBase User Admin.

    • Is there a template I can use to construct my inventory load file?

      Yes, there's a template available HERE. You can click on the shown option to download an example and use it as a template to build out your inventory load .zip file.

    • How do I choose the Inventory load type when consuming the Inventory upload service?

      The inventory load type is controlled by the set value for ACTION_CODE value found in your .DAT file.
      You can only use one action code per file upload. The available options are below:

      • • A = Adds parts to existing inventory.
      • • R = Replaces all existing inventory with the parts in the file.
      • • U = Updates the parts in the file.
      • • D = Deletes all the parts in the file.

    • What is the difference between PULL RFQs and PUSH RFQs service?

      • PULL RFQ — This service returns Seller’s RFQs based on the parameters selected.
      • PUSH RFQ — This service sends Seller’s RFQs every 3 min to the sellers API endpoint.

    • Does Pull RFQ also return Overhaul RFQs?

      Yes, on the response there will be a value for <IsOverhaul> that will indicate if the RFQ is related to Overhaul.