Hi, the documentation here mentions you can embed the token in the URL:
$ curl 'https://elastic.snaplogic.com/api/1/rest/slsched/feed/example/jobs/test-hello?Name=John&bearer_token=Xrcuwn2zVLqR7KXXXXXXXXX'
{ "msg" : "Hello, John!" }
It doesn't seem to work for me. I get a 404.
Authorization header does work but adding to the URL still returns a 404
I understand you're experiencing an issue where authorization headers work correctly, but adding authorization parameters to the URL still returns a 404 error. This is a common scenario when working with REST APIs in SnapLogic. Let me search for information about URL-based authentication and 404 troubleshooting to help you resolve this issue. Based on the search results, it appears you're experiencing a common authentication issue with REST APIs. The fact that the authorization header works but adding to the URL returns a 404 suggests a few potential causes: Common Causes and Solutions 1. URL Structure Issues - 404 errors typically indicate the endpoint URL is incorrect or the resource doesn't exist - When adding authentication parameters to the URL (as query parameters), you might be changing the endpoint path in a way the server doesn't recognize - Verify the exact URL format expected by the API documentation 2. Authentication Method Mismatch The API might be designed to only accept authentication via headers, not URL parameters. Many REST APIs have specific requirements: - Header-based authentication: Authorization: Bearer <token> or Authorization: <api-key> - Query parameter authentication: ?api_key=<key> or ?token=<token> Some APIs support both methods, while others are strict about which method to use. 3. Configuration Recommendations If you're using SnapLogic REST Snaps, consider these approaches: For API Key Authentication: - Use the API Key Authenticator policy if you're working with API Management - Configure the key location as either: - Custom Header Keys (recommended for security) - Custom Query String Parameters (if the API specifically requires it) For OAuth2 Authentication: - Use REST OAuth2 Account types - Ensure the Header authenticated checkbox is selected for bearer token authentication 4. Security Best Practice As noted in the search results: "Avoid passing sensitive information in query parameters since query parameters appear in logs and other locations." Recommendation: Stick with header-based authentication when it works, as it's more secure than URL parameters. 5. Troubleshooting Steps 1. Check the API documentation for the exact authentication method required 2. Verify the endpoint URL is correct when adding query parameters 3. Test with a tool like Postman to confirm the expected behavior 4. Check if the API requires specific parameter names (e.g., api_key vs token vs key) Would you like me to help you configure a specific authentication method in SnapLogic, or do you need assistance troubleshooting the exact URL format for your API?
Encoding was the issue. Example in documentation is poor and doesn't work. Removed and started again and it was fine.
I understand you encountered an encoding issue and found that the documentation example wasn't helpful. It sounds like you resolved it by starting fresh, which is often a good troubleshooting approach! Encoding issues can be tricky in data integration pipelines. If you'd like, I can help you with: - Understanding encoding best practices in SnapLogic pipelines - Troubleshooting specific encoding scenarios you might encounter in the future - Finding better documentation or examples for encoding-related tasks - Configuring Snaps to handle different character encodings properly Is there a particular aspect of encoding handling you'd like guidance on, or would you like me to search for better examples and documentation around encoding in SnapLogic?
Hi Milo. Thanks for reaching out. I believe you were looking at a prior version of the Triggered Task doc, accessible from the Confluence version history. This is the latest version. However, we will work with our team and update the example as required.
I see you've shared what appears to be a message about updating documentation for Triggered Tasks. However, I'm not sure how I can help you with this specific message. Are you looking for: 1. Information about Triggered Tasks - how they work, how to configure them, or best practices? 2. Help with a specific Triggered Task implementation - creating or modifying a pipeline that uses triggered tasks? 3. Documentation or examples related to Triggered Tasks? 4. Something else entirely related to this message? Could you clarify what you'd like assistance with regarding Triggered Tasks or SnapLogic in general? I'm here to help with pipeline development, SnapLogic features, expressions, and other platform-related questions.