{"files":{"SKILL.md":"---\nname: ats-api\ndescription: \"ATS API skill. Use when working with ATS for ats. Covers 15 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# ATS API\nAPI version: 10.24.12\n\n## Auth\nApiKey Authorization in header\n\n## Base URL\nhttps://unify.apideck.com\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /ats/jobs -- list jobs\n3. POST /ats/jobs -- create first job\n\n## Endpoints\n15 endpoints across 1 group. See references/api-spec.lap for full details.\n\n### Ats\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /ats/jobs | List Jobs |\n| POST | /ats/jobs | Create Job |\n| GET | /ats/jobs/{id} | Get Job |\n| PATCH | /ats/jobs/{id} | Update Job |\n| DELETE | /ats/jobs/{id} | Delete Job |\n| GET | /ats/applicants | List Applicants |\n| POST | /ats/applicants | Create Applicant |\n| GET | /ats/applicants/{id} | Get Applicant |\n| PATCH | /ats/applicants/{id} | Update Applicant |\n| DELETE | /ats/applicants/{id} | Delete Applicant |\n| GET | /ats/applications | List Applications |\n| POST | /ats/applications | Create Application |\n| GET | /ats/applications/{id} | Get Application |\n| PATCH | /ats/applications/{id} | Update Application |\n| DELETE | /ats/applications/{id} | Delete Application |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all jobs?\" -> GET /ats/jobs\n- \"Create a job?\" -> POST /ats/jobs\n- \"Get job details?\" -> GET /ats/jobs/{id}\n- \"Partially update a job?\" -> PATCH /ats/jobs/{id}\n- \"Delete a job?\" -> DELETE /ats/jobs/{id}\n- \"List all applicants?\" -> GET /ats/applicants\n- \"Create a applicant?\" -> POST /ats/applicants\n- \"Get applicant details?\" -> GET /ats/applicants/{id}\n- \"Partially update a applicant?\" -> PATCH /ats/applicants/{id}\n- \"Delete a applicant?\" -> DELETE /ats/applicants/{id}\n- \"List all applications?\" -> GET /ats/applications\n- \"Create a application?\" -> POST /ats/applications\n- \"Get application details?\" -> GET /ats/applications/{id}\n- \"Partially update a application?\" -> PATCH /ats/applications/{id}\n- \"Delete a application?\" -> DELETE /ats/applications/{id}\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Paginated endpoints accept limit/offset or cursor parameters\n- Create/update endpoints return the modified resource on success\n- Error responses include status codes and descriptions in the spec\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api ATS API\n@base https://unify.apideck.com\n@version 10.24.10\n@auth ApiKey Authorization in header\n@common_fields {x-apideck-consumer-id: str # ID of the consumer which you want to get or push data from, x-apideck-app-id: str # The ID of your Unify application, raw: bool=false # Include raw response. Mostly used for debugging purposes, x-apideck-service-id: str # Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.}\n@endpoints 15\n@toc ats(15)\n\n@endpoint GET /ats/jobs\n@desc List Jobs\n@optional {cursor: str # Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response., limit: int=20 # Number of results to return. Minimum 1, Maximum 200, Default 20, pass_through: map # Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads, fields: str # The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city`In the example above, the response will only include the fields \"name\", \"email\" and \"addresses.city\". If any other fields are available, they will be excluded.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: [map], _raw: map?, meta: map{items_on_page: int, cursors: map{previous: str?, current: str?, next: str?}}, links: map{previous: str?, current: str, next: str?}} # Jobs\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint POST /ats/jobs\n@desc Create Job\n@optional {id: str # A unique identifier for an object., slug: str, title: str # The job title of the person., sequence: int # Sequence in relation to other jobs., visibility: str(draft/public/internal) # The visibility of the job, status: str(draft/internal/published/completed/placed/on-hold/private/accepting_candidates/open/closed/archived) # The status of the job., code: str # The code of the job., language: str # language code according to ISO 639-1. For the United States - EN, employment_terms: str(full-time/part-time/internship/contractor/employee/freelance/temp/seasonal/volunteer/other), experience: str # Level of experience required for the job role., location: str # Specifies the location for the job posting., remote: bool # Specifies whether the posting is for a remote job., requisition_id: str # A job's Requisition ID (Req ID) allows your organization to identify and track a job based on alphanumeric naming conventions unique to your company's internal processes., department: map{id: str, parent_id: str, name: str, code: str, description: str, custom_mappings: map, updated_by: str, created_by: str, updated_at: str(date-time), created_at: str(date-time), pass_through: [map]}, branch: map{id: str, name: str} # Details of the branch for which the job is created., recruiters: [str] # The recruiter is generally someone who is tasked to help the hiring manager find and screen qualified applicant, hiring_managers: [str], followers: [str], description: str # A description of the object., description_html: str # The job description in HTML format, blocks: [any], closing: str, closing_html: str # The closing section of the job description in HTML format, closing_date: str(date), salary: map{min: int, max: int, currency: str, interval: str}, url: str # URL of the job description, job_portal_url: str # URL of the job portal, record_url: str, links: [map{type: str, url: str}], confidential: bool, available_to_employees: bool # Specifies whether an employee of the organization can apply for the job., tags: [str], addresses: [map{id: str, type: str, string: str, name: str, line1: str, line2: str, line3: str, line4: str, line5: str, street_number: str, city: str, state: str, postal_code: str, country: str, latitude: str, longitude: str, county: str, contact_name: str, salutation: str, phone_number: str, fax: str, email: str, website: str, notes: str, row_version: str}], custom_fields: [map{id: str, name: str, description: str, value: any}], deleted: bool # Flag to indicate if the object is deleted., owner_id: str, published_at: str(date-time), custom_mappings: map # When custom mappings are configured on the resource, the result is included here., updated_by: str # The user who last updated the object., created_by: str # The user who created the object., updated_at: str(date-time) # The date and time when the object was last updated., created_at: str(date-time) # The date and time when the object was created.}\n@returns(201) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Jobs\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ats/jobs/{id}\n@desc Get Job\n@required {id: str # ID of the record you are acting upon.}\n@optional {fields: str # The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city`In the example above, the response will only include the fields \"name\", \"email\" and \"addresses.city\". If any other fields are available, they will be excluded.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, slug: str?, title: str?, sequence: int, visibility: str, status: str, code: str, language: str?, employment_terms: str?, experience: str, location: str?, remote: bool?, requisition_id: str, department: map{id: str, parent_id: str?, name: str?, code: str?, description: str?, custom_mappings: map?, updated_by: str?, created_by: str?, updated_at: str(date-time)?, created_at: str(date-time)?, pass_through: [map]}, branch: map{id: str, name: str}, recruiters: [str]?, hiring_managers: [str], followers: [str]?, description: str?, description_html: str?, blocks: [any], closing: str?, closing_html: str?, closing_date: str(date)?, salary: map{min: int, max: int, currency: str?, interval: str?}, url: str?, job_portal_url: str?, record_url: str?, links: [map], confidential: bool, available_to_employees: bool, tags: [str]?, addresses: [map], custom_fields: [map], deleted: bool?, owner_id: str?, published_at: str(date-time)?, custom_mappings: map?, updated_by: str?, created_by: str?, updated_at: str(date-time)?, created_at: str(date-time)?}, _raw: map?} # Jobs\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint PATCH /ats/jobs/{id}\n@desc Update Job\n@required {id: str # ID of the record you are acting upon.}\n@optional {id: str # A unique identifier for an object., slug: str, title: str # The job title of the person., sequence: int # Sequence in relation to other jobs., visibility: str(draft/public/internal) # The visibility of the job, status: str(draft/internal/published/completed/placed/on-hold/private/accepting_candidates/open/closed/archived) # The status of the job., code: str # The code of the job., language: str # language code according to ISO 639-1. For the United States - EN, employment_terms: str(full-time/part-time/internship/contractor/employee/freelance/temp/seasonal/volunteer/other), experience: str # Level of experience required for the job role., location: str # Specifies the location for the job posting., remote: bool # Specifies whether the posting is for a remote job., requisition_id: str # A job's Requisition ID (Req ID) allows your organization to identify and track a job based on alphanumeric naming conventions unique to your company's internal processes., department: map{id: str, parent_id: str, name: str, code: str, description: str, custom_mappings: map, updated_by: str, created_by: str, updated_at: str(date-time), created_at: str(date-time), pass_through: [map]}, branch: map{id: str, name: str} # Details of the branch for which the job is created., recruiters: [str] # The recruiter is generally someone who is tasked to help the hiring manager find and screen qualified applicant, hiring_managers: [str], followers: [str], description: str # A description of the object., description_html: str # The job description in HTML format, blocks: [any], closing: str, closing_html: str # The closing section of the job description in HTML format, closing_date: str(date), salary: map{min: int, max: int, currency: str, interval: str}, url: str # URL of the job description, job_portal_url: str # URL of the job portal, record_url: str, links: [map{type: str, url: str}], confidential: bool, available_to_employees: bool # Specifies whether an employee of the organization can apply for the job., tags: [str], addresses: [map{id: str, type: str, string: str, name: str, line1: str, line2: str, line3: str, line4: str, line5: str, street_number: str, city: str, state: str, postal_code: str, country: str, latitude: str, longitude: str, county: str, contact_name: str, salutation: str, phone_number: str, fax: str, email: str, website: str, notes: str, row_version: str}], custom_fields: [map{id: str, name: str, description: str, value: any}], deleted: bool # Flag to indicate if the object is deleted., owner_id: str, published_at: str(date-time), custom_mappings: map # When custom mappings are configured on the resource, the result is included here., updated_by: str # The user who last updated the object., created_by: str # The user who created the object., updated_at: str(date-time) # The date and time when the object was last updated., created_at: str(date-time) # The date and time when the object was created.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Jobs\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint DELETE /ats/jobs/{id}\n@desc Delete Job\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Jobs\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ats/applicants\n@desc List Applicants\n@optional {cursor: str # Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response., limit: int=20 # Number of results to return. Minimum 1, Maximum 200, Default 20, filter: map # Apply filters, pass_through: map # Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads, fields: str # The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city`In the example above, the response will only include the fields \"name\", \"email\" and \"addresses.city\". If any other fields are available, they will be excluded.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: [map], _raw: map?, meta: map{items_on_page: int, cursors: map{previous: str?, current: str?, next: str?}}, links: map{previous: str?, current: str, next: str?}} # Applicants\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint POST /ats/applicants\n@desc Create Applicant\n@optional {id: str # A unique identifier for an object., name: str # The name of an applicant., salutation: str # A formal salutation for the person. For example, 'Mr', 'Mrs', first_name: str # The first name of the person., last_name: str # The last name of the person., middle_name: str # Middle name of the person., initials: str # The initials of the person, usually derived from their first, middle, and last names., birthday: str(date) # The date of birth of the person., gender: str(male/female/unisex/other/not_specified) # The gender represents the gender identity of a person., social_security_number: str # A unique identifier assigned by the government. This field is considered sensitive information and may be subject to special security and privacy restrictions., type: str, cover_letter: str, job_url: str, photo_url: str # The URL of the photo of a person., headline: str # Typically a list of previous companies where the contact has worked or schools that the contact has attended, title: str # The job title of the person., emails: [map{id: str, email!: str(email), type: str}], custom_fields: [map{id: str, name: str, description: str, value: any}], phone_numbers: [map{id: str, country_code: str, area_code: str, number!: str, extension: str, type: str}], addresses: [map{id: str, type: str, string: str, name: str, line1: str, line2: str, line3: str, line4: str, line5: str, street_number: str, city: str, state: str, postal_code: str, country: str, latitude: str, longitude: str, county: str, contact_name: str, salutation: str, phone_number: str, fax: str, email: str, website: str, notes: str, row_version: str}], websites: [map{id: str, url!: str, type: str}], social_links: [map{id: str, url!: str, type: str}], stage_id: str, recruiter_id: str, coordinator_id: str, application_ids: [str], applications: [str] # Deprecated: Use application_ids instead. Array of application IDs associated with the applicant., followers: [str], sources: [str], source_id: str, confidential: bool, anonymized: bool, tags: [str], archived: bool, last_interaction_at: str(date-time), owner_id: str, sourced_by: str, cv_url: str, record_url: str, rejected_at: str(date-time), custom_mappings: map # When custom mappings are configured on the resource, the result is included here., deleted: bool # Flag to indicate if the object is deleted., deleted_by: str # The user who deleted the object., deleted_at: str(date-time) # The time at which the object was deleted., updated_by: str # The user who last updated the object., created_by: str # The user who created the object., updated_at: str(date-time) # The date and time when the object was last updated., created_at: str(date-time) # The date and time when the object was created., pass_through: [map{service_id!: str, operation_id: str, extend_object: map, extend_paths: [map]}] # The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources.}\n@returns(201) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Applicants\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ats/applicants/{id}\n@desc Get Applicant\n@required {id: str # ID of the record you are acting upon.}\n@optional {fields: str # The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city`In the example above, the response will only include the fields \"name\", \"email\" and \"addresses.city\". If any other fields are available, they will be excluded.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, name: str, salutation: str?, first_name: str?, last_name: str?, middle_name: str?, initials: str?, birthday: str(date)?, gender: str?, social_security_number: str?, type: str, cover_letter: str, job_url: str?, photo_url: str?, headline: str, title: str?, emails: [map], custom_fields: [map], phone_numbers: [map], addresses: [map], websites: [map], social_links: [map], stage_id: str, recruiter_id: str, coordinator_id: str, application_ids: [str]?, applications: [str]?, followers: [str]?, sources: [str]?, source_id: str, confidential: bool, anonymized: bool, tags: [str]?, archived: bool?, last_interaction_at: str(date-time)?, owner_id: str?, sourced_by: str?, cv_url: str, record_url: str?, rejected_at: str(date-time)?, custom_mappings: map?, deleted: bool?, deleted_by: str?, deleted_at: str(date-time)?, updated_by: str?, created_by: str?, updated_at: str(date-time)?, created_at: str(date-time)?, pass_through: [map]}, _raw: map?} # Applicants\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint PATCH /ats/applicants/{id}\n@desc Update Applicant\n@required {id: str # ID of the record you are acting upon.}\n@optional {id: str # A unique identifier for an object., name: str # The name of an applicant., salutation: str # A formal salutation for the person. For example, 'Mr', 'Mrs', first_name: str # The first name of the person., last_name: str # The last name of the person., middle_name: str # Middle name of the person., initials: str # The initials of the person, usually derived from their first, middle, and last names., birthday: str(date) # The date of birth of the person., gender: str(male/female/unisex/other/not_specified) # The gender represents the gender identity of a person., social_security_number: str # A unique identifier assigned by the government. This field is considered sensitive information and may be subject to special security and privacy restrictions., type: str, cover_letter: str, job_url: str, photo_url: str # The URL of the photo of a person., headline: str # Typically a list of previous companies where the contact has worked or schools that the contact has attended, title: str # The job title of the person., emails: [map{id: str, email!: str(email), type: str}], custom_fields: [map{id: str, name: str, description: str, value: any}], phone_numbers: [map{id: str, country_code: str, area_code: str, number!: str, extension: str, type: str}], addresses: [map{id: str, type: str, string: str, name: str, line1: str, line2: str, line3: str, line4: str, line5: str, street_number: str, city: str, state: str, postal_code: str, country: str, latitude: str, longitude: str, county: str, contact_name: str, salutation: str, phone_number: str, fax: str, email: str, website: str, notes: str, row_version: str}], websites: [map{id: str, url!: str, type: str}], social_links: [map{id: str, url!: str, type: str}], stage_id: str, recruiter_id: str, coordinator_id: str, application_ids: [str], applications: [str] # Deprecated: Use application_ids instead. Array of application IDs associated with the applicant., followers: [str], sources: [str], source_id: str, confidential: bool, anonymized: bool, tags: [str], archived: bool, last_interaction_at: str(date-time), owner_id: str, sourced_by: str, cv_url: str, record_url: str, rejected_at: str(date-time), custom_mappings: map # When custom mappings are configured on the resource, the result is included here., deleted: bool # Flag to indicate if the object is deleted., deleted_by: str # The user who deleted the object., deleted_at: str(date-time) # The time at which the object was deleted., updated_by: str # The user who last updated the object., created_by: str # The user who created the object., updated_at: str(date-time) # The date and time when the object was last updated., created_at: str(date-time) # The date and time when the object was created., pass_through: [map{service_id!: str, operation_id: str, extend_object: map, extend_paths: [map]}] # The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Applicants\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint DELETE /ats/applicants/{id}\n@desc Delete Applicant\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Applicants\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ats/applications\n@desc List Applications\n@optional {cursor: str # Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response., pass_through: map # Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads, limit: int=20 # Number of results to return. Minimum 1, Maximum 200, Default 20}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: [map], _raw: map?, meta: map{items_on_page: int, cursors: map{previous: str?, current: str?, next: str?}}, links: map{previous: str?, current: str, next: str?}} # Applications\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint POST /ats/applications\n@desc Create Application\n@required {applicant_id: str, job_id: str}\n@optional {id: str # A unique identifier for an object., status: str(open/rejected/hired/converted/other), stage: map{id: str, name: str}, custom_mappings: map # When custom mappings are configured on the resource, the result is included here., updated_by: str # The user who last updated the object., created_by: str # The user who created the object., updated_at: str(date-time) # The date and time when the object was last updated., created_at: str(date-time) # The date and time when the object was created., pass_through: [map{service_id!: str, operation_id: str, extend_object: map, extend_paths: [map]}] # The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources.}\n@returns(201) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Applications\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint GET /ats/applications/{id}\n@desc Get Application\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str, applicant_id: str?, job_id: str?, status: str?, stage: map{id: str?, name: str?}, custom_mappings: map?, updated_by: str?, created_by: str?, updated_at: str(date-time)?, created_at: str(date-time)?, pass_through: [map]}, _raw: map?} # Applications\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint PATCH /ats/applications/{id}\n@desc Update Application\n@required {id: str # ID of the record you are acting upon., applicant_id: str, job_id: str}\n@optional {id: str # A unique identifier for an object., status: str(open/rejected/hired/converted/other), stage: map{id: str, name: str}, custom_mappings: map # When custom mappings are configured on the resource, the result is included here., updated_by: str # The user who last updated the object., created_by: str # The user who created the object., updated_at: str(date-time) # The date and time when the object was last updated., created_at: str(date-time) # The date and time when the object was created., pass_through: [map{service_id!: str, operation_id: str, extend_object: map, extend_paths: [map]}] # The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Applications\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@endpoint DELETE /ats/applications/{id}\n@desc Delete Application\n@required {id: str # ID of the record you are acting upon.}\n@returns(200) {status_code: int, status: str, service: str, resource: str, operation: str, data: map{id: str}, _raw: map?} # Applications\n@errors {400: Bad Request, 401: Unauthorized, 402: Payment Required, 404: The specified resource was not found, 422: Unprocessable}\n\n@end\n"}}