We are looking for a skilled and energetic individual to join our team as the chief bottle open officer. This unique role requires precision, attention to detail, and the ability to handle a high volume of beverage bottles in a fast-paced environment. The ideal candidate will ensure bottles are opened swiftly and safely while maintaining hygiene standards.
location: type: - object - 'null' properties: street_1: type: - string - 'null' description: >- If we can parse the address data, this field contains the first part of the street information. street_2: type: - string - 'null' city: type: - string - 'null' state: type: - string - 'null' zip_code: type: - string - 'null' country: type: - string - 'null' description: >- Contains the ISO2 country code if possible. If not, it contains the original value. raw: type: - string - 'null' description: >- If we have address data, this is filled with the raw address string. description: The job location information. hiring_team: type: array items: type: object properties: remote_id: type: - string - 'null' description: >- The team member's identifier in the integrated system. examples: - '78901' email: type: - string - 'null' description: The team member's email address. examples: - jane.doe@gmail.com first_name: type: - string - 'null' description: The team member's first name. examples: - Jane last_name: type: - string - 'null' description: The team member's last name. examples: - Doe hiring_team_roles: type: array items: type: string enum: - RECRUITER - HIRING_MANAGER examples: - RECRUITER description: >- Array of the roles of the user for this specific job. examples: - - RECRUITER required: - remote_id - email - first_name - last_name - hiring_team_roles description: A member of the hiring team. description: >- The hiring team allows you to provision users into your system who can access the job and its applications. required: - remote_id - name - job_code - description - location - hiring_team description: Information about the job posting. required: - id - package_id - candidate - application - job examples: - id: B5KQKhAgTv6ZwzrfAbqbhipd package_id: typescript_test candidate: remote_id: '12345' email: john.doe@gmail.com first_name: John last_name: Doe phone: +1 123 456 7890 application: remote_id: '54321' job: remote_id: '67890' name: Bottle Opener job_code: BO-2024-01 description: >-We are looking for a skilled and energetic individual to join our team as the chief bottle open officer. This unique role requires precision, attention to detail, and the ability to handle a high volume of beverage bottles in a fast-paced environment. The ideal candidate will ensure bottles are opened swiftly and safely while maintaining hygiene standards.
location: street_1: Lohmühlenstraße 65 street_2: null city: Berlin state: Berlin zip_code: '12435' country: DE raw: Berlin, Germany hiring_team: - remote_id: '78901' email: jane.doe@gmail.com first_name: Jane last_name: Doe hiring_team_roles: - RECRUITER required: - next - results required: - status - data responses: ErrorResponseATS: description: The standard error response with the error codes for the ATS use case. content: application/json: schema: type: object properties: status: type: string enum: - error error: type: object properties: code: type: - string - 'null' enum: - PLATFORM.RATE_LIMIT_EXCEEDED - PLATFORM.CONCURRENCY_LIMIT_EXCEEDED - PLATFORM.INTEGRATION_NOT_FOUND - PLATFORM.INPUT_INVALID - PLATFORM.UNKNOWN_ERROR - PLATFORM.IP_NOT_WHITELISTED - PLATFORM.AUTHENTICATION_INVALID - PLATFORM.TASK_TIMED_OUT - INTEGRATION.PERMISSION_MISSING - INTEGRATION.AUTHENTICATION_INVALID - INTEGRATION.QA_FAILED - INTEGRATION.SETUP_SYNC_PENDING - INTEGRATION.SETUP_INCOMPLETE - INTEGRATION.INACTIVE - INTEGRATION.MODEL_NOT_AVAILABLE - INTEGRATION.MODEL_DISABLED - INTEGRATION.ACTION_NOT_AVAILABLE - INTEGRATION.ACTION_DISABLED - REMOTE.SERVICE_UNAVAILABLE - REMOTE.RATE_LIMIT_EXCEEDED - REMOTE.INPUT_INVALID - REMOTE.UNKNOWN_HTTP_ERROR - ATS.JOB_CLOSED - ATS.APPLICATION_ALREADY_EXISTS example: ATS.JOB_CLOSED description: >- Some errors include an error code that can be used to identify their cause. See the [Error Handling Docs](https://docs.kombo.dev/guides/errors) for more information. For your error handling logic please use the error `code` instead of other properties (e.g. message, http status code, ...). title: type: - string - 'null' description: A static, human-readable label. message: type: string description: >- A dynamic, detailed description of what went wrong in this specific instance. log_url: type: - string - 'null' format: uri description: >- The log page in the Kombo UI lists every interaction with full details. If you need assistance, share that link with our support team. required: - code - title - message - log_url description: Error details with structured code for programmatic handling. required: - status - error examples: Error Response: description: >- When building error handling logic, always use the `code` field to identify specific error types programmatically. See the complete list of error codes in the [docs](https://docs.kombo.dev/guides/errors). value: status: error error: code: INTEGRATION.MODEL_NOT_AVAILABLE title: >- This data model isn't supported for the selected integration. message: >- The "employees" model is not yet available for Greenhouse. Please reach out to Kombo if you need this functionality. log_url: https://app.kombo.dev/my-prod/logs?interactionId=123456 Minimal Error Response: description: >- The "message" is always required while other fields can also be `null`. See the [docs](https://docs.kombo.dev/guides/errors) for more information. value: status: error error: code: null title: null message: The message is always in the response. log_url: null securitySchemes: ApiKey: type: http scheme: bearer description: >- Create an API key on the [Secrets](https://app.kombo.dev/secrets) page in the Kombo dashboard. ````