Thanks for all your help. Turns out the string is very space sensitive and the boundery set in the header should not contain --. Now it works! Thanks to your replies I could focus more specifically on the problem.
Yes, but maybe some layout is not correct. If you say this is the right way, I will first try to see if I can make it work. Thanks for now and I will post my outcome here
I maybe found the information you wanted me to see, but than I have the same question, how do I implement it.POST /parse/image HTTP/1.1Host: api.ocr.spaceContent-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Length: 870474----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="language"dut----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="isOverlayRequired"false----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="issearchablepdfhidetextlayer"false----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="iscreatesearchablepdf"false----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="filetype"When I create the content input like this:----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="language"dut----WebKitFormBoundary7MA4YWxkTrZu0gWContent-Disposition: form-data; name="isOverlayRequired"false----WebKitFormBoundary7MA4YWxkTrZu0g
Hi Anne, thanks for your quick reply. I saw those, but (and maybe it is just me) but I do not know how to translate that to the input parameters of the HTTP-Connector. F.e. can you tell me how to translate underlying cURL code into the parameters of the HTTP-Connector? Especially the --form is something I do not know what to do with. Thanks in advance! curl --location --request POST 'https://api.ocr.space/parse/image' \--header 'Content-Type: multipart/form-data;boundary=abcde12345' \--form 'language="dut"' \--form 'isOverlayRequired="false"' \--form 'issearchablepdfhidetextlayer="false"' \--form 'iscreatesearchablepdf="false"' \--form 'filetype="application/pdf"' \Â
Â
Hi Erwin, thanks. I already tried that, but I did not get it to work. I will try to solve it this way. If I don’t succeed I will post here again. Thanks for now.
Thanks, but I do not want to tell a website builder to make use of the staging functionality. I just want him to give one endpoint of the corresponding task, which works perfectly except for the process flow. Then, the functionality would be the same for the windows GUI and the API. As ThinkWise states in its documentation for resource staging: "For example, when Indicium is called automatically by a third party application or service or by some scheduled process. In these cases, when there is no need to indicate to some user whether or not input fields are mandatory, disabled etcetera, a record can still be saved in a single request." That sound logical to me. But this single task request should also trigger any process flows attached to it.I do not understand why I need to do this in another way. At this moment I have one task for a subscription and I should not create a API flow to be able to do the same. Do you have any other suggestions?
Hi Mark, thanks for you reply. Can you help me than with my problem? Maybe this should not be in this thread, but you can probably move it. My problem is this. I have a subscription task subscription_task (i.e. name, email) and in the Process Flow I defined a flow that when this task is executed, a mail should be send (in my case via HTTP connector). When I execute this task in the windows GUI, everything goes well and I receive an email. However, if I execute its API endpoint (http://…………/subscription_task) then the task is executed well, but the email is not sent. So the behaviour of the windows GUI task and the API counterpart is different. Can you help me with this?
I was searching for process flow start by executing a table task. Read this thread. Is it true that we still can not expect the flow to start if we execute the task via the API? I think this should get more priority, because now we cannot expect the API to behave the same as the GUI’s. That seems as a great liability to me. Is this correct or do I miss something and should it work? I am running Indicium version 2022.1
Thanks for your reply. Gave my upvote to the other story.
Yes, partly, but then for mobile GUI. I don't know when the mobile GUI will be updated to universal.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
