Overview
When integrating with the Supplier.io API, users may occasionally encounter issues that affect API responses or the results returned. These issues are often related to request formatting, environment usage, supplier data provided in the request, or default field values.
This article outlines common API issues and provides troubleshooting tips to help identify and resolve them quickly.
For detailed request structures and field definitions, please refer to the API documentation:
- Production API documentation: https://api.supplier.io/Supplier/
- Implementation API documentation: https://api.supplierio.com/supplier/
Results Differ Between API Environments
One common source of confusion occurs when results from the Implementation (test) environment differ from those returned by the Production environment.
Because the Implementation environment is intended for testing purposes, it may not always reflect the most current data available in Production.
If you notice differences in supplier classifications or returned results:
- Confirm which environment your API request is using
- Validate final results using the Production environment
- Review the appropriate API documentation for the environment being used
You can also refer to “API: Production vs Implementation Environment – What’s the Difference?” for more information.
Unexpected Record Usage
Customers may occasionally see differences between the number of suppliers submitted and the number of records counted toward their API limits.
API usage is based on unique suppliers submitted, rather than the total number of rows included in requests.
To ensure suppliers are correctly identified:
- Provide a unique inputSupplierId for each supplier
- Use consistent identifiers across requests
- Avoid reusing the same identifier for different suppliers
Additional information can be found in “API Record Limits and How Usage Is Counted.”
Suppliers Not Returning Expected Results[GD1]
In some cases, an API request may complete successfully but return limited or unexpected supplier data.
This can occur when the supplier information provided in the request is incomplete or inconsistent.
To improve matching accuracy:
- Include as much supplier information as possible
- Provide location information such as address, city, state, and country
- Verify supplier names are spelled correctly
- Avoid submitting incomplete supplier records when possible
Providing more detailed supplier information generally improves match accuracy.
Default Field Values
Some API fields are optional but have default values that may affect results if not explicitly included in the request.
For example, the field enableSelfCertified is set to FALSE by default. If this field is not included in the request, self-certified designations will not be returned in the response.
If you are expecting specific types of certifications or designations, it may be helpful to review the default values of optional fields and adjust your request accordingly.
The API documentation for each environment provides additional details about available fields and their default behavior.
Request Formatting Issues
API requests may fail or return incomplete responses if the request format does not match the expected structure.
If you encounter errors when submitting requests:
- Confirm that all required fields are included
- Verify that field names match the API specification
- Ensure that request payloads follow the expected JSON structure
- Review the API documentation for the correct request format
When to Contact Support
If you continue to experience issues after reviewing the steps above, please contact support@supplier.io.
When reaching out, it can be helpful to include:
- The environment used (Production or Implementation)
- A sample API request
- The response returned by the API
- Any supplier records used in testing
Providing this information helps our team investigate and resolve issues more efficiently.