Aggregator’s SpinnerChief integration allows you to automatically “spin” or rewrite imported content, generating unique versions of articles. However, if you’re encountering issues with the SpinnerChief API not functioning correctly, this guide provides troubleshooting steps to help you identify and resolve common problems.
Common Symptoms of API Issues
Before diving into troubleshooting, let’s review some common symptoms of API issues with the SpinnerChief integration:
- Content isn’t being spun: Imported articles are displayed as they originally appear, without any modifications.
- Error messages: You may see error messages related to API connectivity, such as “API request failed” or “Invalid API key.”
- No response from the SpinnerChief service: The plugin may indicate that it’s attempting to spin content but doesn’t produce any changes.
If you’re experiencing any of these symptoms, follow the steps below to diagnose and resolve the issue.
Verify Your API Key and Account
The first step is to confirm that your SpinnerChief API key is active and correct:
- Check your Spinner Chief account: Ensure that your API subscription is active and that you have sufficient credits, as certain subscription levels or insufficient credits may prevent the API from working.
- Confirm the API key: Go to
Aggregator>Settings>SpinnerChiefand verify that the API key you entered matches the one provided in your SpinnerChief account. Any typos or incorrect characters could cause the integration to fail. - Test your API key: Log into SpinnerChief’s API documentation page, if available, and test the API key to ensure it works outside of Aggregator.
Review API Settings and Limits
SpinnerChief’s API may have usage limits, such as the number of requests allowed per day. Review the following:
- Usage limits: Check your SpinnerChief account for any daily limits or restrictions on API calls. If limits have been exceeded, spinning may not work until the next reset period.
- Request delays: Some accounts may need a delay between API calls to avoid rate limiting. Aggregator’s Update Strategy settings allow you to control import frequency, which can help avoid exceeding SpinnerChief’s limits.
Test the API Connection
If your API key is correct, the next step is to test the connection between Aggregator and SpinnerChief:
- Check server connectivity: Some hosting providers block certain API requests for security reasons. Contact your hosting provider to confirm that connections to the Spinner Chief API endpoint are allowed.
- Disable security plugins temporarily: Security plugins may sometimes interfere with API requests. Temporarily disable any security plugins and test the API again to see if the issue is resolved. Preferably, do this on a staging site so as not to affect the live site.
- Use a test request: In some cases, a simple test request to the Spinner Chief API endpoint may reveal connection issues. If possible and if you know how, use a tool like Postman or curl to send a request and confirm the API’s availability.
Update or Reauthorize API Access
If none of the above steps resolve the issue, you may need to reauthorize or refresh your API access:
- Regenerate API key: Log in to your SpinnerChief account, generate a new API key, and update this in
Aggregator>Settings>SpinnerChief. - Clear cache: If you use a caching plugin or server cache, clear it to ensure that no outdated API data is causing conflicts.
- Update Aggregator and SpinnerChief: Ensure both Aggregator’s free and premium plugins are up to date. Compatibility issues with older versions can sometimes affect API functionality.
Check for Plugin Conflicts
Sometimes, conflicts with other plugins can disrupt API functionality. To identify any conflicting plugins, please follow our conflict testing guide.
Contact Support
If the SpinnerChief API still isn’t working after following all of the above steps, consider reaching out to SpinnerChief support and our support team with as much detail as possible about what’s happening on your site.
