Using Flow token leads to "error HTTP/1.1 404 Not Found

Document ID : KB000047643
Last Modified Date : 14/02/2018
Show Technical Document Details


Different Flow Tokens in CA Flowdock


Using either own code or the example from?
the user will receive a response similar to this:?

HTTP/1.1 404 Not Found
Date: Tue, 15 Mar 2016 08:47:58 GMT
Server: Apache
Status: 404 Not Found
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
x-trace-id: 547f6e7d-7e3f-4ffb-810d-c906c2d1af86
x-parent-id: 5abfc8df-26ab-477f-853e-0775cc14f03f
Rate-Limit-Limit: 150
Rate-Limit-Remaining: 149
Content-Type: application/json; charset=utf-8
Cache-Control: private, no-store, no-cache
X-Request-Id: 95e5a49b-f344-4e7d-affc-83341532614f
X-Runtime: 0.017046
Strict-Transport-Security: max-age=31557600
X-Server-Id: 475b6e71889f174f61273dab9d11d64422779f4c
Transfer-Encoding: chunked

{"message":"Not found"}



The API Flow token was used instead of the Source Flow Token.

The API Flow Token can be found at?
These tokens can be used to access a specific flow. But these are deprecated and the user should make use of message endpoints.?
The example in the mentioned page is making use of these message endpoints.

The Source Flow Token is a token specific to a single Source (Integration) that has been setup for a specific flow.



To create a Source Flow token, a Developer Application must be created and a source generated (
1. Create the Developer Application on that page.?
2. On the application page, scroll down to create a new source
3. Give a name and select a flow for the source, click on Generate Source
4. Note down the resulting Source Flow Token