This forum is used to ask questions regarding the Standard Integrations
UserID infomartapiuser2 --- deleted
Standard Integration QuestionsHi,
Was provided the below sandbox/api credentials.
Username: infomartapiuser2
Password: ********
Customer ID: 6270
Sandbox URL: https://partnerscreeningsandbox.icims.com/
While creating a new Job, under Assignment/Secondary Recruiter, do not see infomartapiuser2 in the dropdown list? Can you check if infomartapiuser2 exists?
Thanks
- Read more about UserID infomartapiuser2 --- deleted
- Log in to post comments
SandBox Testing. Getting "You do not have permission to access this profile due to search locks"
Standard Integration QuestionsHi,
Was able to retrieve candidate ID 2969 (url:https://api.icims.com/customers/6271/people/2969) via postman.
After editing Candidate ID 2969 (logging into the sandbox and tried to add phone/address/school/license) got the error "You do not have permission to access this profile due to search locks" while saving and as well doing a people search by typing in '2969' in the search window.
Maintenance
Standard Integration QuestionsHi
Despite the fact that we request a JSON content via the Header `Content-Type: application/json`, we receive HTML when receiving "Service temporarily unavailable" error.
Would it be possible to receive JSON as documented on https://developer.icims.com/icims-platform/error-handling?
Best,
- Read more about Maintenance
- 1 comment
- Log in to post comments
New Integration Questions SASS
Standard Integration Questions• I am assuming just like in the current integration we will have the option to store and associate different locations (ie cust-numbers) and package numbers from our side to the rec? These will be associated to the rec and included with the data set for the candidate background request. This information is necessary to tell us what to order and where to put it.
- Read more about New Integration Questions SASS
- 1 comment
- Log in to post comments
Background Check Results and Status URL
Standard Integration QuestionsHello,
We provide background check details to our clients by exposing a POST REST endpoint.
In the payload we expect XML with credentials (client name, password, and some candidate ID).
How can ICIMS platform users access this endpoint?
When we do patches to update the background check status, we can send a link:
Order Status: In-Progress Vendor
Result URL: {BACKGROUND CHECK STATUS LINK HERE}
according to: https://developer.icims.com/Standard-Integrations/Partner-Screening
- Read more about Background Check Results and Status URL
- 1 comment
- Log in to post comments
Is it possible to delete a Binary File via the API?
Standard Integration QuestionsIs it possible to delete a Binary File via the API?
Using Third Party Plugin for MS SQL Integration Service to Connect to API EndPoints
Standard Integration QuestionsWithin the plugin there is a preview section that works great after configuring the URLs, Authorization header, etc.
Outside the preview section when executing the whole ETL process I get a HTTP Error Code 406.
Looking around I found out this
"The resource identified by the request cannot provide any of the acceptable content-types specified in the Accept header of the client request."
Any suggestion on what entries are needed on my header to make this work?
Using MS SQL integration services with ICIMS EndPoints
Standard Integration QuestionsJust checking if anyone was able to successfully connect a SSIS Script Task with ICIMS Endpoints.
You do not have permission to access this profile due to search locks.
Standard Integration QuestionsHave a new sandbox to do a standard integration however creating a new candidate results in an error styled message box with the contents: "You do not have permission to access this profile due to search locks."
Replying to ICIMS with an Error Message
Standard Integration QuestionsHi,
I need to send back an error message to ICIMS.
I followed the instructions on https://developer.icims.com/REST-API/Error-Handling-and-Reporting but I still can't see the error messages.
This is the json message I am sending:
{
"error": {
"userMessage": "Invalid fields - Bad applicant last name.",
"debugErrorMessage": "Invalid fields - Bad applicant last name."
}
}
Thank you.
- Read more about Replying to ICIMS with an Error Message
- 4 comments
- Log in to post comments