apply_joborder without ID

[TBP]

The 'ID' parameter for https://api.catsone.com/api/apply_joborder is not required, and omitting it gives the option to apply a joborder when no ID is available. However, when the ID is removed from the POST parameters, a strange (seemingly unrelated) error message is returned:

Email and password are required parameters for registrations.

What is the right approach? Should 'ID' be set to a default value?

[Aaron Baluczynski]

Hi,

If you leave off the job order ID it acts as a "general registration." This means you must submit all the questions for the general registration application, plus "email" and "password" parameters.

Aaron

[TBP]

Thanks for the reply. The desired behavior is indeed to 'generally' apply for jobs that are coming up, without applying for a specific job.

What is the expected value of the 'password' parameter? Since a website visitor has no knowledge of the CATS mechanisms behind an application form that's pulled in through the API, and just wants to submit a general application.

Op donderdag 20 oktober 2016 20:34:08 UTC+2 schreef Aaron Baluczynski:

[Aaron Baluczynski]

The "password" field is the same as the "password" field on the general registration on the career portal. It is the password the applicant chooses to use to login to the portal at a later date.

[TBP]

I understand. Is there any way to retrieve the actual registration form (from the /index.php?m=portal&a=register link at the portal) instead? This way, the user can provide a password.

Op dinsdag 25 oktober 2016 16:15:45 UTC+2 schreef Aaron Baluczynski:

[Aaron Baluczynski]

I'm not sure what you're asking. It seems like all you need to do is add an input for the password and send that along with the API request.

Aaron

[Aaron Baluczynski]

I apologize if I am in error, but I get the sense that maybe you are posting the form from the user directly to the API in the browser. Is this correct?

[TBP]

Thanks for the clarification about adding the password field to the API response ourselves.

About the form: we're not sending the POST data to CATS in the browser itself, but on the server side after submitting.

Op woensdag 26 oktober 2016 16:16:22 UTC+2 schreef Aaron Baluczynski:

[Aaron Baluczynski]

Okay, good! I just wanted to make sure.

[TBP]

Got around to testing this, but if I create the two fields and the following is added to the POST body (with real data), the same error appears:

'email'    => 'in...@example.com'

'password' => 'xxxxxx'

`Email and password are required parameters for registrations`. What am I doing wrong?

Op woensdag 26 oktober 2016 16:14:17 UTC+2 schreef Aaron Baluczynski:

[Aaron Baluczynski]

That looks correct. Are you sure that is actually being posted?

I have tested on my end, and the following works as expected:

http://api.catsone.com/api/apply_joborder?subdomain=abc&transaction_code=123456&id=&email=te...@catsone.com&password=test123456&1294016=First&1294019=Last