What should I provide when reporting a MerchantSpring API issue?

A general description such as 'the API is not working' usually does not provide enough information to reproduce the issue. Send the exact request and response details so MerchantSpring Support can identify the likely cause.

Information to include

• Your MerchantSpring user email and account/company
• The endpoint and request method
• The exact request or cURL with the API key redacted
• All relevant parameters, headers and filters
• The full response body and HTTP status
• The result you expected
• The approximate date, time and timezone
• Whether the same request works in the API documentation's testing tool

What does HTTP 200 with no records mean?

HTTP 200 means the request succeeded. The response can still contain no records if the date range or filters do not match available data. Confirm exact marketplace and country values as well as the selected period.

What can HTTP 403 mean?

A 403 Forbidden response can indicate an authentication or authorisation problem. Confirm that the correct valid key is being used and that the user has access, without sending the full key through a support channel.

API key reminder

Replace the key with a placeholder such as YOUR_API_KEY before copying a request into email, chat or a support ticket.

Need more help? Contact MerchantSpring Support at support@merchantspring.io.