Submitting via portal

[t...@forcit.be]

Hi

When I try to submit an application via the portals -> submit endpoint I get an error on any of the file fields. 

I followed the API documentation (https://api.catsone.com/v3/docs/index.html#portals-submit).

When I include the file field, and build the parameters as described it keeps returning me the error 'Upload resume is a required field'. 

But is included in the post body. 

With all the other fields, without file fields, there are no problems. 

This is the body i'll post to the endpoint: (https://api.catsone.nl/v3/portals/PORTAL_ID/jobs/JOB_ID). Offcourse PORTAL_ID and JOB_ID is correct. 

{"fields":[

    {"id":53212,"value":"SGVsbG8gV29ybGQ=","filename":"test.txt"}, /* upload resume file field */

    {"id":53062,"value":"string1"},

    {"id":53065,"value":"string2"},

    {"id":53068,"value":"string3"},

    {"id":53071,"value":"string4"},

    {"id":53074,"value":"string5"},

    {"id":53077,"value":"string6"},

    {"id":53080,"value":"string7"},

    {"id":53083,"value":"string8"},

    {"id":53086,"value":{"167500":true,"167503":true}},

    {"id":53089,"value":{"167455":true,"167470":true}}

]}

The response: 

{

  "message": "Validation failed.",

  "errors": [

    "Upload resume is a required field."

  ]

}

Kind regards

[Anthony Allan]

Hi there,

I took a look at that specific application, and it looks like the resume field id is 53215, not 53212 like you posted above.

[t...@forcit.be]

Hi Anthony

The ID was indeed not correct, I deleted the field and added it again.

The fields are automatically received with their ID's via the API.

With that ID it still does not work. 

{"fields":[

    {"id":53215,"value":"SGVsbG8gV29ybGQ=","filename":"test.txt"},

    {"id":53062,"value":"string"},

    {"id":53065,"value":"string"},

    {"id":53068,"value":"string"},

    {"id":53071,"value":"string"},

    {"id":53074,"value":"string"},

    {"id":53077,"value":"string"},

    {"id":53080,"value":"string"},

    {"id":53083,"value":"string"},

    {"id":53086,"value":{"167500":true,"167503":true}},

    {"id":53089,"value":{"167455":true,"167470":true}}

]}

Response: 

{

  "message": "Validation failed.",

  "errors": [

    "Upload resume is a required field."

  ]

}

Thanks for taking time to look at it. 

Kind regards, 

[Anthony Allan]

Hi Tom,

This is turning out to be a bigger issue than initially expected. We are currently working on a fix for you. Thanks for your patience.

[t...@forcit.be]

Hi Anthony

Allright, looking forward for the fix! 

Kind regards,

[Anthony Allan]

The issue should be resolved now. Let me know if you have any more problem 

[t...@forcit.be]

Hi Anthony

It seems to work for small files and/or text. 

What if I want to send a PDF as a resume? The base64 encoded string is just to large to work properly? 

To send the larger pdf via another endpoint would miss out on the file field the user can add in the question list.

Any solution for this?

Kind regards, 

[Anthony Allan]

Hey Tom,

Looks like there was an issue with bas64 strings over 1 million characters which has been resolved now. I've tested it with pdfs over 10 MB in size, so any resume should work just fine now.

[t...@forcit.be]

Hi Anthony

When I send a request to this endpoint with an pdf in base64_encoded format as the value. I still receive an error. 

It think it has to do with the '\' and so in the base64 string resulting in a not valid json. 

Do i have to encode it to something to send it properly? 

Kind regards, 

[Anthony Allan]

Hi there,

I'm not sure I understand what you mean. There should be no backslashes in the string. A base64 encoded string should only include letters, numbers, underscore, dash, and possibly equals sign.

[t...@forcit.be]

Hi Anthony

The problem is indeed resolved. 

Thanks!

[t...@forcit.be]

Hi Anthony

Was there recent an update? Since today we are getting the same error again. 

It was working perfectly until now. Can you validate this? 

Kind regards, 

[Anthony Allan]

Hi there,

Unfortunately there was a temporary issue that was preventing resume uploads. This has been resolved and it should be working for you again.