Troubleshooting API issues
The Blueworks Live API enables limited interactions such as searching for artifacts, retrieving process details, and initiating work instances. While most responses are returned in JSON format, interpreting these responses correctly is key to successful integration. Use the troubleshooting section to focus on identifying and resolving common issues. The issues that arise during API usage, including authentication errors, token expiration, and rate limiting. It also provides practical examples and guidance to help you troubleshoot effectively and maintain smooth API operations.
Note: API documentation migrated to IBM API Hub
. Find the latest updates and
documentation for Blueworks Live APIs in API Hub.
. Find the latest updates and
documentation for Blueworks Live APIs in API Hub.Common errors and solutions
| Error Code | Description | Possible Cause | Action |
|---|---|---|---|
| 401 Unauthorized | The request lacks valid authentication credentials. |
|
|
| 403 Forbidden | The server processed the request but access is denied. |
|
|
| 429 Too Many Requests | Rate limit exceeded. | Too many requests sent in a short time |
|
| 400 Bad Request | The server might not understand the request. |
|
|
| 500 Internal Server Error | An unexpected error occurred on the server. | Server-side issue |
|
Understanding and resolving API issues
| Action Area | Description |
|---|---|
| Check Token Validity | Ensure that your access token is current and correctly formatted. |
| Verify Permissions | Confirm that the authenticated user has the necessary roles and access rights. |
| Review API Usage | Monitor your request rate and adjust your client to avoid pressing rate limits. |
| Inspect Request Format | Use tools like Postman or curl to validate your request structure. |