Eliminate Manual Application Entry Across Your Recruitment Tech Stack

Implementation Details

Step 1: Capture and Structure Candidate Data

Collect candidate information through your source system (referral portal, form, chatbot, API). Structure the data according to Knit's candidate object requirements: firstName and lastName (required), at least one email address, at least one phone number with type (WORK, PERSONAL, or SKYPE). Optionally include links (portfolio, LinkedIn, GitHub), location details, and any custom fields your ATS supports.

Note platform-specific requirements: Workable, Breezy, and Loxo require the full candidate object and don't support passing an existing candidateId. If you're integrating with these platforms, always collect complete candidate details. Loxo specifically ignores the lastName field, so ensure firstName contains the candidate's full name.

Step 2: Submit Application to ATS

Call the Create Application API (POST https://api.getknit.dev/v1.0/ats.application.create) with the structured candidate data, target jobId, and optional initialStageId to place the candidate at a specific pipeline stage. Include any application question responses using the appropriate question types (TEXT, SINGLE_CHOICE, MULTIPLE_CHOICE, YES_NO, NUMBER, DATE, FILE_UPLOAD, DROPDOWN, RATING_SCALE).

Handle platform-specific considerations:

• For SAP SuccessFactors, pass a dummy value for initialStageId (the platform ignores this parameter)
• For Workday, include countryCodeId in the metaData object
• For Loxo, include resume details in metaData and remember the platform ignores lastName

Set the origin field (AGENCY, REFERRAL, EXTERNAL) to properly attribute the application source for reporting and analytics.

Step 3: Attach Resumes and Supporting Documents

After creating the application, call the Add Attachment API (POST https://api.getknit.dev/v1.0/ats.application.attachment.add) to upload resumes, cover letters, portfolios, or other supporting documents. Reference the newly created application ID and specify the file type.

Important: Several platforms (Lever, Oracle Cloud HCM, TeamTailor, Breezy, Workable, Bullhorn, Ashby, JazzHR) don't honor the fileType parameter, so ensure your file naming conventions are clear. Zoho Recruit limits applications to one document and only accepts document file types (not images or other formats).

Key Data Models and APIs

API/Data Model	Description
POST /v1.0/ats.application.create	Creates new application; requires candidateId OR candidate object (firstName, lastName, email, phone required) plus jobId
POST /v1.0/ats.application.attachment.add	Uploads resumes, cover letters, and documents to applications (fileType not honored by 8 platforms)
application_info	Core application data: id, status (ACTIVE/REJECTED/HIRED), candidate object, jobId, appliedAt, origin (AGENCY/REFERRAL/EXTERNAL), owner, creditedTo
candidate object	Candidate details: firstName, lastName, phones (with types WORK/PERSONAL/SKYPE), emails (with types), links (portfolio, social), location
application_question_responses	Screening question answers supporting 9 types: TEXT, SINGLE_CHOICE, MULTIPLE_CHOICE, YES_NO, NUMBER, DATE, FILE_UPLOAD, DROPDOWN, RATING_SCALE

Wrapping Up

Knit's Create Application API eliminates the manual bottleneck between candidate interest and ATS entry. With support for 30+ platforms including enterprise systems (Workday, SAP SuccessFactors, Oracle Cloud HCM, iCIMS) and modern ATS platforms (Greenhouse, Lever, Ashby, Bullhorn, SmartRecruiters), you build one integration that works across your entire customer base.

Platform-Specific Handling Built In: Knit manages the nuances of each ATS—from Workday's countryCodeId requirements to Loxo's resume metadata expectations—so you don't need conditional logic for each platform. Pass consistent data structures and Knit handles the translation.

Complete Application Packages: Create applications with full candidate details, application question responses, and attached documents in a single workflow. Candidates enter your recruitment pipeline with all the information recruiters need to make informed decisions.

Proper Attribution and Workflow Triggers: Set application origin (agency, referral, external) and initial pipeline stage to ensure proper source reporting and trigger appropriate automated workflows in your ATS.

Stop losing candidates to manual data entry backlogs. Let Knit automate application creation across your recruitment technology stack.