# Fountain Documentation

## API Reference
- [Fountain API Overview](https://developer.fountain.com/reference/overview.md): Fountain's Developer APIs enable Fountain's clients to access and modify their hiring data.  If you are a Fountain partner, please refer to [partners.fountain.com](https://partners.fountain.com) for guides on integrating with Fountain.
- [Connecting a Custom Form](https://developer.fountain.com/reference/connecting-a-custom-form-to-the-onboardiq-applicant-portal.md)
- [Custom Integrations](https://developer.fountain.com/reference/custom-integrations.md)
- [Slack Integration](https://developer.fountain.com/reference/slack-integration.md)
- [Sync with your HRIS](https://developer.fountain.com/reference/sync-with-hris.md)
- [API Deprecations](https://developer.fountain.com/reference/deprecations.md)
- [Frequently Asked Questions](https://developer.fountain.com/reference/frequently-asked-questions.md)
- [Hire API Overview](https://developer.fountain.com/reference/hire-api-overview.md): Fountain's Developer APIs enable Fountain's clients to access and modify their hiring data.  If you are a Fountain partner, please refer to [partners.fountain.com](https://partners.fountain.com) for guides on integrating with Fountain.
- [Rate Limits](https://developer.fountain.com/reference/rate-limitations.md)
- [Tenant API URLs](https://developer.fountain.com/reference/tenant-api-urls.md)
- [Hire Webhooks](https://developer.fountain.com/reference/webhooks.md)
- [Delete an Applicant](https://developer.fountain.com/reference/delete_v2-applicants-id.md): Delete an applicant and their information
- [Get Interview Sessions](https://developer.fountain.com/reference/get_v2-applicants-id-booked-slots.md): Retrieves the interview sessions for an applicant
- [duplicate applicants](https://developer.fountain.com/reference/get_v2-applicants-id-duplicates.md): Returns the duplicate applicants.
- [Get Applicant Files](https://developer.fountain.com/reference/get_v2-applicants-id-secure-documents.md): Accessing secure file uploads from Fountain.
- [Get Transition History](https://developer.fountain.com/reference/get_v2-applicants-id-transitions.md): Retrieve the transition history for an applicant
- [Get Applicant Info](https://developer.fountain.com/reference/get_v2-applicants-id.md): Get an applicant's data as it is stored in Fountain.
- [Get Latest Applicant](https://developer.fountain.com/reference/get_v2-applicants-latest-applicant.md): Get the latest matching applicant
- [List All Applicants](https://developer.fountain.com/reference/get_v2-applicants.md): Get all applicants
- [Trigger file recollection for an applicant](https://developer.fountain.com/reference/post_api-v2-applicants-applicant-id-file-upload-requests.md): Creates a file recollection request for a specific applicant file. This endpoint triggers a recollection process that notifies the applicant to resubmit a file.
- [Bulk Advance Multiple Applicants](https://developer.fountain.com/reference/post_v2-applicants-advance.md): Advance multiple applicants within an opening
- [Bulk Interview Sessions for Multiple Applicants](https://developer.fountain.com/reference/post_v2-applicants-booked-slots.md): Retrieve the interview sessions for all applicants
- [Approve Applicant Documents](https://developer.fountain.com/reference/post_v2-applicants-id-secure-documents-approve.md): Approve multiple applicant documents by their associated data field keys
- [Link Applicant to Files in S3](https://developer.fountain.com/reference/post_v2-applicants-id-secure-documents-link-upload.md): Step 2 of 2 for adding files to an applicant profile.
- [File Upload to S3](https://developer.fountain.com/reference/post_v2-applicants-id-secure-documents-upload.md): Step 1 of 2 for adding files to an applicant profile.
- [Notify applicant](https://developer.fountain.com/reference/post_v2-applicants-notify.md): Notify the applicant via sms and email to continue the application with the PORTAL_URL
- [Bulk Transition History for Multiple Applicants](https://developer.fountain.com/reference/post_v2-applicants-transitions.md): Retrieve the transition history for all applicants
- [Create an Applicant](https://developer.fountain.com/reference/post_v2-applicants.md): Create an applicant
- [Advance an Applicant](https://developer.fountain.com/reference/put_v2-applicants-id-advance.md): Advance an applicant in an opening
- [Update Applicant Info](https://developer.fountain.com/reference/put_v2-applicants-id.md): Update an applicant's information
- [Delete Calendar Slots](https://developer.fountain.com/reference/delete_v2-available-slots-id.md): Destroy calendar slot by the unique identifier
- [List Calendar Slots](https://developer.fountain.com/reference/get_v2-sessions.md): List all booked slots for an account. Option to include unbooked slots as well. Supports filtering on opening and stage as well as pagination
- [List Available Slots](https://developer.fountain.com/reference/get_v2-stages-id-available-slots.md): List all available slots for a given stage
- [Update Calendar Slot](https://developer.fountain.com/reference/patch_v2-available-slots-id.md): Update an existing calendar slot. All fields are optional — only the fields provided will be updated. When updating `max_attendees`, the new value must be greater than 0. If you set it below the current number of booked attendees, existing bookings are preserved and no new bookings will be accepted until `booked_slots_count` drops below the new cap.
- [Book an Available Slot](https://developer.fountain.com/reference/post_v2-available-slots-id-confirm.md): Book an available slot with an applicant
- [Create Calendar Slots](https://developer.fountain.com/reference/post_v2-available-slots.md): Create a new available slot
- [Cancel a booked slot](https://developer.fountain.com/reference/post_v2-booked-slots-id-cancel.md): Cancel a booked slot
- [Get a specific company attribute by type](https://developer.fountain.com/reference/get_v2-company-attributes-type.md): Returns detailed information about a company attribute.
- [List company attributes](https://developer.fountain.com/reference/get_v2-company-attributes.md): Returns a paginated list of company attributes for the account
- [Add values to a company attribute](https://developer.fountain.com/reference/post_v2-company-attributes-type-values.md): Adds a list of values to a company attribute.
- [Create company attribute](https://developer.fountain.com/reference/post_v2-company-attributes.md): Creates a new company attribute with specified type, value_type, and attribute_values
- [List data keys](https://developer.fountain.com/reference/get_v2-data-keys.md): List all data keys on the account. Supports pagination.
- [Download Custom Export](https://developer.fountain.com/reference/get_v2-exports-id.md): Downloading a custom export
- [List all Custom Export Templates](https://developer.fountain.com/reference/get_v2-exports-templates.md): List all Custom Export Templates
- [List Custom Export Templates](https://developer.fountain.com/reference/get_v2-exports.md): List all Custom Exports
- [Download Timestamped Export](https://developer.fountain.com/reference/get_v2-timestamped-exports-id.md): Downloading a timestamped export
- [List All Timestamped Export Templates](https://developer.fountain.com/reference/get_v2-timestamped-exports-templates.md): List All Timestamped Export Templates
- [List Timestamped Export Templates](https://developer.fountain.com/reference/get_v2-timestamped-exports.md): List all timestamped exports
- [Create Custom Export](https://developer.fountain.com/reference/post_v2-exports.md): Create Custom Exports
- [Create Timestamped Export](https://developer.fountain.com/reference/post_v2-timestamped-exports.md): Create Timestamped Exports
- [Delete a Hiring Goal](https://developer.fountain.com/reference/delete_v2-hiring-goals-id.md): Delete an existing Hiring Goal
- [List Hiring Goals](https://developer.fountain.com/reference/get_v2-hiring-goals.md): List all Hiring Goals within your account. Check the example to see all properties available.
- [Assign Company Attributes to Hiring Goals](https://developer.fountain.com/reference/post_v2-hiring-goals-id-company-attributes.md): Assign or remove Company Attributes for a Hiring Goal
- [Create a new hiring goal](https://developer.fountain.com/reference/post_v2-hiring-goals.md): Create a new Hiring Goal
- [Update Hiring Goal](https://developer.fountain.com/reference/put_v2-hiring-goals-id.md): Update an existing Hiring Goal
- [List Labels for Applicant](https://developer.fountain.com/reference/get_v2-applicants-id-labels.md): This lists all labels for an applicant.
- [List All Labels in Stage](https://developer.fountain.com/reference/get_v2-stages-stage-id-labels.md): This method lists all the labels that are available in a specific stage.
- [Update Label for Applicant](https://developer.fountain.com/reference/put_v2-applicants-id-labels-title.md): This method updates a list of labels for an applicant. Use it to delete existing labels for an applicant or add new ones.
- [Delete a Location Group](https://developer.fountain.com/reference/delete_v2-location-groups-id.md): Delete an existing Location Group
- [Delete a Location](https://developer.fountain.com/reference/delete_v2-locations-id.md): Delete an existing Location
- [Retrieve Location Group](https://developer.fountain.com/reference/get_v2-location-groups-id.md): Find a specific Location Group by the unique identifier.
- [List Location Groups](https://developer.fountain.com/reference/get_v2-location-groups.md): List all Location Groups within your account. Check the example to see all properties available.
- [Retrieve Location](https://developer.fountain.com/reference/get_v2-locations-id.md): Find a specific Location by the unique identifier.
- [List Locations](https://developer.fountain.com/reference/get_v2-locations.md): List all Locations within your account. Check the example to see all properties available.
- [Create a new Location Group](https://developer.fountain.com/reference/post_v2-location-groups.md): Create a new Location Group
- [Assign Company Attributes to Location](https://developer.fountain.com/reference/post_v2-locations-id-company-attributes.md): Assign or remove Company Attributes for a Location
- [Create a new Location](https://developer.fountain.com/reference/post_v2-locations.md): Create a new Location
- [Update Location Group](https://developer.fountain.com/reference/put_v2-location-groups-id.md): Update an existing Location Group
- [Update Location](https://developer.fountain.com/reference/put_v2-locations-id.md): Update an existing Location
- [Delete Applicant Note](https://developer.fountain.com/reference/delete_v2-applicants-id-notes-note-id.md): Deleting an Applicant Note
- [Get Applicant Notes](https://developer.fountain.com/reference/get_v2-applicants-id-notes.md): Accessing Applicant Notes
- [Create Applicant Note](https://developer.fountain.com/reference/post_v2-applicants-id-notes.md): Creating Applicant Notes
- [Update Applicant Note](https://developer.fountain.com/reference/put_v2-applicants-id-notes-note-id.md): Updating Applicant Note
- [Delete an opening](https://developer.fountain.com/reference/delete_v2-funnels-id.md): Delete an existing Opening
- [List All Opening Stages](https://developer.fountain.com/reference/get_v2-funnels-funnel-id-stages.md): Retrieves an Opening's stages
- [Retrieve Opening](https://developer.fountain.com/reference/get_v2-funnels-id.md): Find a specific Opening by the unique identifier.
- [List All Openings](https://developer.fountain.com/reference/get_v2-funnels.md): List all Opening(s) within your account. Funnel is used interchangeably with Opening. Each Opening contains information on address, stages in the funnel, location, active status, etc. Check the example to see all properties available.
- [Retrieve stage](https://developer.fountain.com/reference/get_v2-stages-id.md): Retrieves a specific Stage
- [Create a new opening](https://developer.fountain.com/reference/post_v2-funnels.md): Create a new Opening
- [Update opening](https://developer.fountain.com/reference/put_v2-funnels-id.md): Update an existing Opening. When go_enabled is set to true, the opening is deactivated as part of go-enablement (the opening is set to inactive so it can be managed through Hire Go; it can be reactivated after Go is configured). The account must have Hire Go enabled and the opening's workflow must be go-compatible for go_enabled to take effect.
- [Reassign Opening to Different Workflow (Alpha)](https://developer.fountain.com/reference/post_api-v2-openings-workflow-reassignment.md): Takes a stage mapping array to move applicants from one stage to another.  The stage mapping array is an array of hashes with the keys "source" and "destination".  The "source" key is the name of the stage in the source workflow, and the "destination" key is the name of the stage in the destination workflow. This feature is in Alpha, meaning that explicit flags must be set for this endpoint to behave as expected. If you are interested in trying this API, please reach out to your account representative for more information.
- [Assign or remove Company Attributes from an Opening](https://developer.fountain.com/reference/post_v2-openings-id-company-attributes.md): Adds and/or removes Company Attributes from an Opening
- [Remove from Option Bank](https://developer.fountain.com/reference/delete_v2-option-banks-id-remove.md): Remove an Option Bank Option
- [Delete Option Bank](https://developer.fountain.com/reference/delete_v2-option-banks-id.md): Show an Option Banks
- [Get Option Bank](https://developer.fountain.com/reference/get_v2-option-banks-id.md): Show an Option Banks
- [List All Option Banks](https://developer.fountain.com/reference/get_v2-option-banks.md): application/json
- [Create Option Bank](https://developer.fountain.com/reference/post_v2-option-banks.md): Creating Applicant Notes
- [Append to Option Bank](https://developer.fountain.com/reference/put_v2-option-banks-id-append.md): Remove an Option Bank Option
- [Replace Option Bank](https://developer.fountain.com/reference/put_v2-option-banks-id.md): Show an Option Banks
- [Delete a Position](https://developer.fountain.com/reference/delete_v2-positions-id.md): Delete an existing Position
- [Retrieve Position](https://developer.fountain.com/reference/get_v2-positions-id.md): Find a specific Position by the unique identifier.
- [List Positions](https://developer.fountain.com/reference/get_v2-positions.md): List all Positions within your account. Check the example to see all properties available.
- [Assign Company Attributes to Position](https://developer.fountain.com/reference/post_v2-positions-id-company-attributes.md): Assign or remove Company Attributes for a Position
- [Create a new Position](https://developer.fountain.com/reference/post_v2-positions.md): Create a new Position
- [Update Position](https://developer.fountain.com/reference/put_v2-positions-id.md): Update an existing Position
- [Get Worker Info](https://developer.fountain.com/reference/get_v2-workers-id.md): Get Worker Info
- [List Workers](https://developer.fountain.com/reference/get_v2-workers.md): List Workers
- [Update A Worker](https://developer.fountain.com/reference/patch_v2-workers-id.md): Update a worker
- [Activate A Worker](https://developer.fountain.com/reference/post_v2-workers-id-activate.md): Updates workers is_active attribute to true and marks worker as 'Activated' in Posthire. Reapplies recurring checks
- [Deactivate A Worker](https://developer.fountain.com/reference/post_v2-workers-id-deactivate.md): Updates workers is_active attribute to false and marks worker as 'Deactivated' in Posthire. Cancels all active recurring checks and follow-up messages for this applicant.
- [List user roles](https://developer.fountain.com/reference/get_v2-roles.md): List all roles for the account
- [List shifts](https://developer.fountain.com/reference/get_v2-shifts.md): List all shifts on the account. Supports pagination.
- [List Archived Reasons](https://developer.fountain.com/reference/get_v2-archived-reasons.md): List or search all Archived Reasons within your account.
- [List Rejection Reasons](https://developer.fountain.com/reference/get_v2-rejection-reasons.md): List or search all Rejection Reasons within your account.
- [Delete User](https://developer.fountain.com/reference/delete_v2-users-id.md): Deletes a User
- [List User Activities](https://developer.fountain.com/reference/get_v2-user-activities-id.md): Retrieves a user's activities
- [Get user opening access](https://developer.fountain.com/reference/get_v2-users-user-id-opening-access.md)
- [Get Users](https://developer.fountain.com/reference/get_v2-users.md): Accessing all account users
- [Create User](https://developer.fountain.com/reference/post_v2-users.md): Creates a user
- [Update User](https://developer.fountain.com/reference/put_v2-users-id.md): Updating a specific user
- [change user opening access](https://developer.fountain.com/reference/put_v2-users-user-id-opening-access.md): This API is only available if your account is using the workflow system for configuring openings and stages.
- [Delete Webhook Setting](https://developer.fountain.com/reference/delete_v2-webhook-settings-id.md): Delete a webhook setting
- [Retrieve Webhook Setting](https://developer.fountain.com/reference/get_v2-webhook-settings-id.md): Retrieve a specific webhook setting by ID. Includes the authorization_header in the response.
- [List Webhook Settings](https://developer.fountain.com/reference/get_v2-webhook-settings.md): List all webhook settings for the account. Results are paginated.
- [Create Webhook Setting](https://developer.fountain.com/reference/post_v2-webhook-settings.md): Create a new webhook setting. Allowed types:  - **Webhooks::Settings::ApplicantSave** - Fires when an applicant is created or updated - **Webhooks::Settings::ApplicantStateChange** - Fires when an applicant's application state changes - **Webhooks::Settings::Transition** - Fires when an applicant transitions between workflow stages (supports configurable strategies: first, hired, rejected, archived, all, or selected stages) - **Webhooks::Settings::CheckrStatus** - Fires when a Checkr background check status changes (clear, consider, suspended, engaged, pre_adverse, post_adverse, dispute) - **Webhooks::Settings::OnfidoStatus** - Fires when an Onfido identity verification status changes (clear, consider) - **Webhooks::Settings::FunnelSave** - Fires when an opening is created or updated - **Webhooks::Settings::HiringGoalChange** - Fires when a hiring goal is modified - **Webhooks::Settings::PartnerStatus** - Fires when a partner integration status changes - **Webhooks::Settings::FileStatus** - Fires when an uploaded file's status changes - **Webhooks::Settings::PosthireDataCollectionApproval** - Fires when post-hire documents and/or data fields are approved - **Webhooks::Settings::PosthireWorkerActivation** - Fires when a post-hire worker is activated - **Webhooks::Settings::PosthireWorkerDeactivation** - Fires when a post-hire worker is deactivated - **Webhooks::Settings::PosthireDocumentUploaded** - Fires when a document is uploaded for a post-hire worker - **Webhooks::Settings::LocationSave** - Fires when a location is created or updated
- [Delete a Workflow](https://developer.fountain.com/reference/delete_api-v2-workflows-id.md): Delete a Workflow in an Account
- [List all Workflows](https://developer.fountain.com/reference/get_api-v2-workflows.md): List all Workflows in an Account
- [Embedding the Worker Portal](https://developer.fountain.com/reference/embedding-the-worker-portal.md)
- [Partner Tasks](https://developer.fountain.com/reference/partner-tasks.md): Fountain Worker Experience offers a simple way for partners and developers to integrate any custom workflow as an onboard task.
- [Automation Webhooks](https://developer.fountain.com/reference/automation-webhooks.md)
- [Custom Attribute Webhooks](https://developer.fountain.com/reference/custom-attribute-webhooks.md)
- [Compliance External Processing URL — Configuration Guide](https://developer.fountain.com/reference/external-processing-api-compliance.md)
- [Webhooks and External API Calls](https://developer.fountain.com/reference/webhooks-and-external-api-calls.md)
- [Universal Tasks Webhooks (Onboard)](https://developer.fountain.com/reference/universal-tasks-webhooks-onboard.md)
- [API Deprecations](https://developer.fountain.com/reference/wx-api-deprecations.md)
- [Create an allowance and associate it with a location](https://developer.fountain.com/reference/post_api-serviceattendance-processes-allowances-createandassociate.md)
- [Delete one or more allowances](https://developer.fountain.com/reference/post_api-serviceattendance-processes-allowances-deleteanddisassociate.md)
- [Count allowance for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-allowancesettings-location-locationuuid-count.md)
- [Find allowance settings for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-allowancesettings-location-locationuuid.md)
- [Count allowance for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-allowancesettings-locationgroup-locationgroupuuid-count.md)
- [Find allowance settings for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-allowancesettings-locationgroup-locationgroupuuid.md)
- [Clone allowance settings with allowances](https://developer.fountain.com/reference/post_api-serviceattendance-processes-allowancesettings-allowancesettinguuid-clone.md)
- [delete one apikey](https://developer.fountain.com/reference/delete_api-servicesecurity-apikeys-identifier.md): Delete one apikey
- [delete many apikeys](https://developer.fountain.com/reference/delete_api-servicesecurity-apikeys.md): Delete many apikeys using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count apikeys](https://developer.fountain.com/reference/get_api-servicesecurity-apikeys-count.md): Count apikeys (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one apikey](https://developer.fountain.com/reference/get_api-servicesecurity-apikeys-identifier.md): Find one apikey by its unique identifier.
- [find many apikeys](https://developer.fountain.com/reference/get_api-servicesecurity-apikeys.md): Find many apikeys (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [create a new API key based on caller rights](https://developer.fountain.com/reference/post_api-servicesecurity-processes-apikey-generate-integration-useruuid.md)
- [create a new API key based on caller rights](https://developer.fountain.com/reference/post_api-servicesecurity-processes-apikey-generate.md)
- [count assignedTasks](https://developer.fountain.com/reference/get_api-servicetodo-assignedtasks-count.md): Count assignedTasks (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one assignedTask](https://developer.fountain.com/reference/get_api-servicetodo-assignedtasks-identifier.md): Find one assignedTask by its unique identifier.
- [find many assignedTasks](https://developer.fountain.com/reference/get_api-servicetodo-assignedtasks.md): Find many assignedTasks (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing assignedTask](https://developer.fountain.com/reference/patch_api-servicetodo-assignedtasks-identifier.md): Partially update one existing assignedTask
- [partially update many existing assignedTask](https://developer.fountain.com/reference/patch_api-servicetodo-assignedtasks.md): Partially update many existing assignedTask
- [mark an assignedTask as done programmatically](https://developer.fountain.com/reference/post_api-servicetodo-processes-assignedtasks-assignedtaskidentifier-complete.md)
- [mark an webhook assignedTask as done programmatically and resend it](https://developer.fountain.com/reference/post_api-servicetodo-processes-assignedtasks-assignedtaskidentifier-completeandresend.md)
- [trigger the init process of a task again](https://developer.fountain.com/reference/post_api-servicetodo-processes-assignedtasks-assignedtaskidentifier-reinit.md)
- [retrigger an webhook programmatically for an assignedTask](https://developer.fountain.com/reference/post_api-servicetodo-processes-assignedtasks-assignedtaskidentifier-resend.md)
- [trigger the init process of a task again](https://developer.fountain.com/reference/post_api-servicetodo-processes-workers-workeruuid-cleanup.md)
- [count attendanceActivityLogs](https://developer.fountain.com/reference/get_api-serviceattendance-attendanceactivitylog-count.md): Count attendanceActivityLogs (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one attendanceActivityLog](https://developer.fountain.com/reference/get_api-serviceattendance-attendanceactivitylog-identifier.md): Find one attendanceActivityLog by its unique identifier.
- [find many attendanceActivityLogs](https://developer.fountain.com/reference/get_api-serviceattendance-attendanceactivitylog.md): Find many attendanceActivityLogs (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Find attendance policy for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-attendancepolicies-location-locationuuid.md)
- [Find attendance policy for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-attendancepolicies-locationgroup-locationgroupuuid.md)
- [count audienceJobs](https://developer.fountain.com/reference/get_api-serviceworkforce-audiencejobs-count.md): Count audienceJobs (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one audienceJob](https://developer.fountain.com/reference/get_api-serviceworkforce-audiencejobs-identifier.md): Find one audienceJob by its unique identifier.
- [find many audienceJobs](https://developer.fountain.com/reference/get_api-serviceworkforce-audiencejobs.md): Find many audienceJobs (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [count audienceLocations](https://developer.fountain.com/reference/get_api-serviceworkforce-audiencelocations-count.md): Count audienceLocations (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one audienceLocation](https://developer.fountain.com/reference/get_api-serviceworkforce-audiencelocations-identifier.md): Find one audienceLocation by its unique identifier.
- [find many audienceLocations](https://developer.fountain.com/reference/get_api-serviceworkforce-audiencelocations.md): Find many audienceLocations (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [count audienceOpenings](https://developer.fountain.com/reference/get_api-serviceworkforce-audienceopenings-count.md): Count audienceOpenings (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one audienceOpening](https://developer.fountain.com/reference/get_api-serviceworkforce-audienceopenings-identifier.md): Find one audienceOpening by its unique identifier.
- [find many audienceOpenings](https://developer.fountain.com/reference/get_api-serviceworkforce-audienceopenings.md): Find many audienceOpenings (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Fetch a count of audiences](https://developer.fountain.com/reference/get_api-servicepool-audiences-count.md)
- [fetch list of active campaigns for a given audience](https://developer.fountain.com/reference/get_api-servicepool-audiences-identifier-activecampaigns.md)
- [fetch list of contactable worker uuids for audience within a given audience](https://developer.fountain.com/reference/get_api-servicepool-audiences-identifier-workeruuids.md)
- [Retrieve an audience by its unique identifier](https://developer.fountain.com/reference/get_api-servicepool-audiences-identifier.md)
- [fetch list of audiences](https://developer.fountain.com/reference/get_api-servicepool-audiences.md)
- [Find and update an audience](https://developer.fountain.com/reference/patch_api-servicepool-audiences-identifier.md): Partially update one existing audience
- [Update audience via Copilot](https://developer.fountain.com/reference/patch_api-servicepool-copilot-audiences-identifier.md)
- [Create one or multiple audiences](https://developer.fountain.com/reference/post_api-servicepool-audiences.md)
- [Create audiences via Copilot](https://developer.fountain.com/reference/post_api-servicepool-copilot-audiences.md)
- [Create an automatic break rule and associate it with a location](https://developer.fountain.com/reference/post_api-serviceattendance-processes-automaticbreakrules-createandassociate.md)
- [Delete one or more automatic break rules](https://developer.fountain.com/reference/post_api-serviceattendance-processes-automaticbreakrules-deleteanddisassociate.md)
- [Count automatic break rules for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-automaticbreaksettings-location-locationuuid-count.md)
- [Find automatic break settings for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-automaticbreaksettings-location-locationuuid.md)
- [Count automatic break rules for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-automaticbreaksettings-locationgroup-locationgroupuuid-count.md)
- [Find automatic break settings for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-automaticbreaksettings-locationgroup-locationgroupuuid.md)
- [Clone automatic break settings with automatic break rules](https://developer.fountain.com/reference/post_api-serviceattendance-processes-automaticbreaksettings-automaticbreaksettinguuid-clone.md)
- [delete one brand](https://developer.fountain.com/reference/delete_api-serviceorganizations-brands-identifier.md): Delete one brand
- [delete many brands](https://developer.fountain.com/reference/delete_api-serviceorganizations-brands.md): Delete many brands using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count brands](https://developer.fountain.com/reference/get_api-serviceorganizations-brands-count.md): Count brands (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one brand](https://developer.fountain.com/reference/get_api-serviceorganizations-brands-identifier.md): Find one brand by its unique identifier.
- [find many brands](https://developer.fountain.com/reference/get_api-serviceorganizations-brands.md): Find many brands (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [get a company default brand](https://developer.fountain.com/reference/get_api-serviceorganizations-processes-brands-default.md)
- [partially update one existing brand](https://developer.fountain.com/reference/patch_api-serviceorganizations-brands-identifier.md): Partially update one existing brand
- [partially update many existing brand](https://developer.fountain.com/reference/patch_api-serviceorganizations-brands.md): Partially update many existing brand
- [create one or multiple brands](https://developer.fountain.com/reference/post_api-serviceorganizations-brands.md): Create one or multiple brands
- [replace one brand which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-brands-identifier.md): Replace one brand which exists or not
- [replace many brands which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-brands.md): Replace many brands which exists or not
- [count companies](https://developer.fountain.com/reference/get_api-serviceorganizations-companies-count.md): Count companies (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one company](https://developer.fountain.com/reference/get_api-serviceorganizations-companies-identifier.md): Find one company by its unique identifier.
- [find many companies](https://developer.fountain.com/reference/get_api-serviceorganizations-companies.md): Find many companies (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing company](https://developer.fountain.com/reference/patch_api-serviceorganizations-companies-identifier.md): Partially update one existing company
- [partially update many existing company](https://developer.fountain.com/reference/patch_api-serviceorganizations-companies.md): Partially update many existing company
- [Submit SMS brand registration for a company](https://developer.fountain.com/reference/post_api-serviceorganizations-processes-companies-companyuuid-smsregistration.md)
- [replace one company which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-companies-identifier.md): Replace one company which exists or not
- [replace many companies which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-companies.md): Replace many companies which exists or not
- [delete one companyAttribute](https://developer.fountain.com/reference/delete_api-serviceorganizations-companyattributes-identifier.md): Delete one companyAttribute
- [delete many companyAttributes](https://developer.fountain.com/reference/delete_api-serviceorganizations-companyattributes.md): Delete many companyAttributes using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count companyAttributes](https://developer.fountain.com/reference/get_api-serviceorganizations-companyattributes-count.md): Count companyAttributes (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one companyAttribute](https://developer.fountain.com/reference/get_api-serviceorganizations-companyattributes-identifier.md): Find one companyAttribute by its unique identifier.
- [find many companyAttributes](https://developer.fountain.com/reference/get_api-serviceorganizations-companyattributes.md): Find many companyAttributes (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing companyAttribute](https://developer.fountain.com/reference/patch_api-serviceorganizations-companyattributes-identifier.md): Partially update one existing companyAttribute
- [partially update many existing companyAttribute](https://developer.fountain.com/reference/patch_api-serviceorganizations-companyattributes.md): Partially update many existing companyAttribute
- [create one or multiple companyAttributes](https://developer.fountain.com/reference/post_api-serviceorganizations-companyattributes.md): Create one or multiple companyAttributes
- [replace one companyAttribute which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-companyattributes-identifier.md): Replace one companyAttribute which exists or not
- [replace many companyAttributes which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-companyattributes.md): Replace many companyAttributes which exists or not
- [delete one companyAttributeSet](https://developer.fountain.com/reference/delete_api-serviceorganizations-companyattributesets-identifier.md): Delete one companyAttributeSet
- [delete many companyAttributeSets](https://developer.fountain.com/reference/delete_api-serviceorganizations-companyattributesets.md): Delete many companyAttributeSets using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count companyAttributeSets](https://developer.fountain.com/reference/get_api-serviceorganizations-companyattributesets-count.md): Count companyAttributeSets (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one companyAttributeSet](https://developer.fountain.com/reference/get_api-serviceorganizations-companyattributesets-identifier.md): Find one companyAttributeSet by its unique identifier.
- [find many companyAttributeSets](https://developer.fountain.com/reference/get_api-serviceorganizations-companyattributesets.md): Find many companyAttributeSets (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing companyAttributeSet](https://developer.fountain.com/reference/patch_api-serviceorganizations-companyattributesets-identifier.md): Partially update one existing companyAttributeSet
- [partially update many existing companyAttributeSet](https://developer.fountain.com/reference/patch_api-serviceorganizations-companyattributesets.md): Partially update many existing companyAttributeSet
- [create one or multiple companyAttributeSets](https://developer.fountain.com/reference/post_api-serviceorganizations-companyattributesets.md): Create one or multiple companyAttributeSets
- [replace one companyAttributeSet which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-companyattributesets-identifier.md): Replace one companyAttributeSet which exists or not
- [replace many companyAttributeSets which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-companyattributesets.md): Replace many companyAttributeSets which exists or not
- [delete one copilotAuditLog](https://developer.fountain.com/reference/delete_api-serviceorganizations-copilotauditlogs-identifier.md): Delete one copilotAuditLog
- [delete many copilotAuditLogs](https://developer.fountain.com/reference/delete_api-serviceorganizations-copilotauditlogs.md): Delete many copilotAuditLogs using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count copilotAuditLogs](https://developer.fountain.com/reference/get_api-serviceorganizations-copilotauditlogs-count.md): Count copilotAuditLogs (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one copilotAuditLog](https://developer.fountain.com/reference/get_api-serviceorganizations-copilotauditlogs-identifier.md): Find one copilotAuditLog by its unique identifier.
- [find many copilotAuditLogs](https://developer.fountain.com/reference/get_api-serviceorganizations-copilotauditlogs.md): Find many copilotAuditLogs (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing copilotAuditLog](https://developer.fountain.com/reference/patch_api-serviceorganizations-copilotauditlogs-identifier.md): Partially update one existing copilotAuditLog
- [partially update many existing copilotAuditLog](https://developer.fountain.com/reference/patch_api-serviceorganizations-copilotauditlogs.md): Partially update many existing copilotAuditLog
- [create one or multiple copilotAuditLogs](https://developer.fountain.com/reference/post_api-serviceorganizations-copilotauditlogs.md): Create one or multiple copilotAuditLogs
- [replace one copilotAuditLog which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-copilotauditlogs-identifier.md): Replace one copilotAuditLog which exists or not
- [replace many copilotAuditLogs which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-copilotauditlogs.md): Replace many copilotAuditLogs which exists or not
- [delete one customAttribute](https://developer.fountain.com/reference/delete_api-serviceworkforce-customattributes-identifier.md): Delete one customAttribute
- [delete many customAttributes](https://developer.fountain.com/reference/delete_api-serviceworkforce-customattributes.md): Delete many customAttributes using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count customAttributes](https://developer.fountain.com/reference/get_api-serviceworkforce-customattributes-count.md): Count customAttributes (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one customAttribute](https://developer.fountain.com/reference/get_api-serviceworkforce-customattributes-identifier.md): Find one customAttribute by its unique identifier.
- [find many customAttributes](https://developer.fountain.com/reference/get_api-serviceworkforce-customattributes.md): Find many customAttributes (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing customAttribute](https://developer.fountain.com/reference/patch_api-serviceworkforce-customattributes-identifier.md): Partially update one existing customAttribute
- [partially update many existing customAttribute](https://developer.fountain.com/reference/patch_api-serviceworkforce-customattributes.md): Partially update many existing customAttribute
- [create one or multiple customAttributes](https://developer.fountain.com/reference/post_api-serviceworkforce-customattributes.md): Create one or multiple customAttributes
- [replace one customAttribute which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-customattributes-identifier.md): Replace one customAttribute which exists or not
- [replace many customAttributes which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-customattributes.md): Replace many customAttributes which exists or not
- [delete one defaultNotificationTemplate](https://developer.fountain.com/reference/delete_api-servicepulse-defaultnotificationtemplates-identifier.md): Delete one defaultNotificationTemplate
- [delete many defaultNotificationTemplates](https://developer.fountain.com/reference/delete_api-servicepulse-defaultnotificationtemplates.md): Delete many defaultNotificationTemplates using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count defaultNotificationTemplates](https://developer.fountain.com/reference/get_api-servicepulse-defaultnotificationtemplates-count.md): Count defaultNotificationTemplates (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one defaultNotificationTemplate](https://developer.fountain.com/reference/get_api-servicepulse-defaultnotificationtemplates-identifier.md): Find one defaultNotificationTemplate by its unique identifier.
- [find many defaultNotificationTemplates](https://developer.fountain.com/reference/get_api-servicepulse-defaultnotificationtemplates.md): Find many defaultNotificationTemplates (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing defaultNotificationTemplate](https://developer.fountain.com/reference/patch_api-servicepulse-defaultnotificationtemplates-identifier.md): Partially update one existing defaultNotificationTemplate
- [partially update many existing defaultNotificationTemplate](https://developer.fountain.com/reference/patch_api-servicepulse-defaultnotificationtemplates.md): Partially update many existing defaultNotificationTemplate
- [create one or multiple defaultNotificationTemplates](https://developer.fountain.com/reference/post_api-servicepulse-defaultnotificationtemplates.md): Create one or multiple defaultNotificationTemplates
- [Creates bulk demand for a given period](https://developer.fountain.com/reference/post_api-serviceattendance-processes-demand-bulkcreate.md)
- [Creates shifts for a specific demand or list of demands](https://developer.fountain.com/reference/post_api-serviceattendance-processes-demand-createshifts.md)
- [count demands](https://developer.fountain.com/reference/get_api-serviceattendance-demands-count.md): Count demands (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one demand](https://developer.fountain.com/reference/get_api-serviceattendance-demands-identifier.md): Find one demand by its unique identifier.
- [find many demands](https://developer.fountain.com/reference/get_api-serviceattendance-demands.md): Find many demands (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Retrieve a documentSubmission by its unique identifier](https://developer.fountain.com/reference/get_api-servicecompliancev2-documentsubmissions-identifier.md)
- [fetch list of documentSubmissions](https://developer.fountain.com/reference/get_api-servicecompliancev2-documentsubmissions.md)
- [Create one documentSubmission](https://developer.fountain.com/reference/post_api-servicecompliancev2-documentsubmissions.md)
- [Find and update a documentSubmission](https://developer.fountain.com/reference/put_api-servicecompliancev2-documentsubmissions-identifier.md): Partially update one existing documentSubmission
- [Retreive a documentType by its unique identifier](https://developer.fountain.com/reference/get_api-servicecompliancev2-documenttypes-identifier.md)
- [fetch list of documentTypes](https://developer.fountain.com/reference/get_api-servicecompliancev2-documenttypes.md)
- [Create one or multiple documentTypes simplified](https://developer.fountain.com/reference/post_api-servicecompliancev2-ai-documenttypes.md)
- [Create one or multiple documentTypes](https://developer.fountain.com/reference/post_api-servicecompliancev2-documenttypes.md)
- [delete one ein](https://developer.fountain.com/reference/delete_api-serviceorganizations-eins-identifier.md): Delete one ein
- [delete many eins](https://developer.fountain.com/reference/delete_api-serviceorganizations-eins.md): Delete many eins using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count eins](https://developer.fountain.com/reference/get_api-serviceorganizations-eins-count.md): Count eins (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one ein](https://developer.fountain.com/reference/get_api-serviceorganizations-eins-identifier.md): Find one ein by its unique identifier.
- [find many eins](https://developer.fountain.com/reference/get_api-serviceorganizations-eins.md): Find many eins (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing ein](https://developer.fountain.com/reference/patch_api-serviceorganizations-eins-identifier.md): Partially update one existing ein
- [partially update many existing ein](https://developer.fountain.com/reference/patch_api-serviceorganizations-eins.md): Partially update many existing ein
- [Update one or multiple existing Employer Identification Numbers (EINs) metadata](https://developer.fountain.com/reference/patch_api-serviceorganizations-processes-mcp-eins.md)
- [create one or multiple eins](https://developer.fountain.com/reference/post_api-serviceorganizations-eins.md): Create one or multiple eins
- [replace one ein which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-eins-identifier.md): Replace one ein which exists or not
- [replace many eins which exists or not](https://developer.fountain.com/reference/put_api-serviceorganizations-eins.md): Replace many eins which exists or not
- [count employerNotes](https://developer.fountain.com/reference/get_api-serviceemployment-employernotes-count.md): Count employerNotes (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one employerNote](https://developer.fountain.com/reference/get_api-serviceemployment-employernotes-identifier.md): Find one employerNote by its unique identifier.
- [find many employerNotes](https://developer.fountain.com/reference/get_api-serviceemployment-employernotes.md): Find many employerNotes (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [create one or multiple employerNotes](https://developer.fountain.com/reference/post_api-serviceemployment-employernotes.md): Create one or multiple employerNotes
- [delete one employer](https://developer.fountain.com/reference/delete_api-servicestaff-employers-identifier.md): Delete one employer
- [delete many employers](https://developer.fountain.com/reference/delete_api-servicestaff-employers.md): Delete many employers using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count employers](https://developer.fountain.com/reference/get_api-servicestaff-employers-count.md): Count employers (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one employer](https://developer.fountain.com/reference/get_api-servicestaff-employers-identifier.md): Find one employer by its unique identifier.
- [find many employers](https://developer.fountain.com/reference/get_api-servicestaff-employers.md): Find many employers (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing employer](https://developer.fountain.com/reference/patch_api-servicestaff-employers-identifier.md): Partially update one existing employer
- [partially update many existing employer](https://developer.fountain.com/reference/patch_api-servicestaff-employers.md): Partially update many existing employer
- [create one or multiple employers](https://developer.fountain.com/reference/post_api-servicestaff-employers.md): Create one or multiple employers
- [replace one employer which exists or not](https://developer.fountain.com/reference/put_api-servicestaff-employers-identifier.md): Replace one employer which exists or not
- [replace many employers which exists or not](https://developer.fountain.com/reference/put_api-servicestaff-employers.md): Replace many employers which exists or not
- [count employmentProfiles](https://developer.fountain.com/reference/get_api-serviceemployment-employmentprofiles-count.md): Count employmentProfiles (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one employmentProfile](https://developer.fountain.com/reference/get_api-serviceemployment-employmentprofiles-identifier.md): Find one employmentProfile by its unique identifier.
- [find many employmentProfiles](https://developer.fountain.com/reference/get_api-serviceemployment-employmentprofiles.md): Find many employmentProfiles (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Get worker W-4 document assignments](https://developer.fountain.com/reference/get_api-serviceemployment-processes-companies-companyidentifier-profiles-w4-workers-workeridentifier-assignments.md)
- [partially update one existing employmentProfile](https://developer.fountain.com/reference/patch_api-serviceemployment-employmentprofiles-identifier.md): Partially update one existing employmentProfile
- [partially update many existing employmentProfile](https://developer.fountain.com/reference/patch_api-serviceemployment-employmentprofiles.md): Partially update many existing employmentProfile
- [Set the disabled flag for a worker case and emit activity events](https://developer.fountain.com/reference/patch_api-serviceemployment-processes-companies-companyidentifier-profiles-all-workers-workeridentifier-disabled.md)
- [Update allowed properties for an employment profile](https://developer.fountain.com/reference/patch_api-serviceemployment-processes-companies-companyidentifier-profiles-all-workers-workeridentifier.md)
- [Update tags associated to a profile](https://developer.fountain.com/reference/patch_api-serviceemployment-processes-companies-companyidentifier-profiles-i9-workers-workeridentifier-tags.md)
- [Rehire a profile submission(s)](https://developer.fountain.com/reference/post_api-serviceemployment-processes-companies-companyidentifier-profiles-i9-workers-workeridentifier-rehire.md)
- [Restart a profile submission(s)](https://developer.fountain.com/reference/post_api-serviceemployment-processes-companies-companyidentifier-profiles-i9-workers-workeridentifier-restart.md)
- [count generalSettings](https://developer.fountain.com/reference/get_api-serviceattendance-generalsettings-count.md): Count generalSettings (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one generalSetting](https://developer.fountain.com/reference/get_api-serviceattendance-generalsettings-identifier.md): Find one generalSetting by its unique identifier.
- [find many generalSettings](https://developer.fountain.com/reference/get_api-serviceattendance-generalsettings.md): Find many generalSettings (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [/api/serviceattendance/processes/generalSettings](https://developer.fountain.com/reference/get_api-serviceattendance-processes-generalsettings.md)
- [Update holiday rule(s) and invalidate overlapping schedules for re-evaluation](https://developer.fountain.com/reference/patch_api-serviceattendance-processes-holidayrules-updateholidayrules.md)
- [Create a holiday rule and associate it with a location](https://developer.fountain.com/reference/post_api-serviceattendance-processes-holidayrules-createandassociate.md)
- [Delete one or more holiday rules](https://developer.fountain.com/reference/post_api-serviceattendance-processes-holidayrules-deleteanddisassociate.md)
- [Get active holiday rules for specified locations within a date range](https://developer.fountain.com/reference/post_api-serviceattendance-processes-holidayrules-getactiveholidayrulesforlocations.md)
- [Delete holiday rule settings and re-evaluate workers for inheritance](https://developer.fountain.com/reference/delete_api-serviceattendance-processes-holidayrulesettings-holidayrulesettinguuid.md): Deletes local holiday rule settings and triggers re-evaluation of workers against inherited rules. Used when switching from local settings to inherited settings.
- [Count holiday rule settings for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-holidayrulesettings-location-locationuuid-count.md)
- [Find holiday rule settings for a given location](https://developer.fountain.com/reference/get_api-serviceattendance-processes-holidayrulesettings-location-locationuuid.md)
- [Count holiday rule settings for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-holidayrulesettings-locationgroup-locationgroupuuid-count.md)
- [Find holiday rule settings for a given location group](https://developer.fountain.com/reference/get_api-serviceattendance-processes-holidayrulesettings-locationgroup-locationgroupuuid.md)
- [Clone holiday rule settings](https://developer.fountain.com/reference/post_api-serviceattendance-processes-holidayrulesettings-holidayrulesettinguuid-clone.md)
- [One stop setup for I9Center V2](https://developer.fountain.com/reference/post_api-serviceemployment-processes-i9center-setup.md)
- [delete one job](https://developer.fountain.com/reference/delete_api-serviceworkforce-jobs-identifier.md): Delete one job
- [delete many jobs](https://developer.fountain.com/reference/delete_api-serviceworkforce-jobs.md): Delete many jobs using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count jobs](https://developer.fountain.com/reference/get_api-serviceworkforce-jobs-count.md): Count jobs (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one job](https://developer.fountain.com/reference/get_api-serviceworkforce-jobs-identifier.md): Find one job by its unique identifier.
- [find many jobs](https://developer.fountain.com/reference/get_api-serviceworkforce-jobs.md): Find many jobs (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing job](https://developer.fountain.com/reference/patch_api-serviceworkforce-jobs-identifier.md): Partially update one existing job
- [partially update many existing job](https://developer.fountain.com/reference/patch_api-serviceworkforce-jobs.md): Partially update many existing job
- [Update a job and replace its Company Attributes with the payload](https://developer.fountain.com/reference/patch_api-serviceworkforce-processes-jobs-jobuuid-custom-attributes.md): Updates a Job and upserts its Company Attributes. The provided customAttributesPayload replaces the entire set of attributes attached to the job: any attribute not present in the payload will be removed; provided ones will be created/updated. Values must match the attribute data type configured for the company attribute.
- [create one or multiple jobs](https://developer.fountain.com/reference/post_api-serviceworkforce-jobs.md): Create one or multiple jobs
- [Create a job and replace its Company Attributes with the payload](https://developer.fountain.com/reference/post_api-serviceworkforce-processes-jobs-custom-attributes.md): Creates a Job and upserts its Company Attributes in one request. The provided customAttributesPayload replaces the entire set of attributes attached to the job: attributes omitted from the payload will be removed, attributes present will be created/updated. Values must match the attribute data type configured for the company attribute.
- [replace one job which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-jobs-identifier.md): Replace one job which exists or not
- [replace many jobs which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-jobs.md): Replace many jobs which exists or not
- [Update a location group and replace its Company Attributes with the payload](https://developer.fountain.com/reference/patch_api-serviceworkforce-processes-locationgroups-locationgroupuuid-custom-attributes.md): Updates a Location Group and upserts its Company Attributes. The provided customAttributesPayload replaces the entire set of attributes attached to the location group: omit the field to leave existing attributes unchanged; provide an empty array ([]) to remove all attributes from the location group. Values must match the attribute data type configured for the company attribute.
- [Create a location group and replace its Company Attributes with the payload](https://developer.fountain.com/reference/post_api-serviceworkforce-processes-locationgroups-custom-attributes.md): Creates a Location Group and upserts its Company Attributes in one request. The provided customAttributesPayload replaces the entire set of attributes attached to the location group: omit the field to create the location group without company attributes; provide an empty array ([]) to create the location group with no attributes. Values must match the attribute data type configured for the company attribute.
- [delete one locationGroup](https://developer.fountain.com/reference/delete_api-serviceworkforce-locationgroups-identifier.md): Delete one locationGroup
- [delete many locationGroups](https://developer.fountain.com/reference/delete_api-serviceworkforce-locationgroups.md): Delete many locationGroups using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count locationGroups](https://developer.fountain.com/reference/get_api-serviceworkforce-locationgroups-count.md): Count locationGroups (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one locationGroup](https://developer.fountain.com/reference/get_api-serviceworkforce-locationgroups-identifier.md): Find one locationGroup by its unique identifier.
- [find many locationGroups](https://developer.fountain.com/reference/get_api-serviceworkforce-locationgroups.md): Find many locationGroups (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing locationGroup](https://developer.fountain.com/reference/patch_api-serviceworkforce-locationgroups-identifier.md): Partially update one existing locationGroup
- [partially update many existing locationGroup](https://developer.fountain.com/reference/patch_api-serviceworkforce-locationgroups.md): Partially update many existing locationGroup
- [create one or multiple locationGroups](https://developer.fountain.com/reference/post_api-serviceworkforce-locationgroups.md): Create one or multiple locationGroups
- [replace one locationGroup which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-locationgroups-identifier.md): Replace one locationGroup which exists or not
- [replace many locationGroups which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-locationgroups.md): Replace many locationGroups which exists or not
- [count locationGroupTrees](https://developer.fountain.com/reference/get_api-serviceworkforce-locationgrouptrees-count.md): Count locationGroupTrees (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one locationGroupTree](https://developer.fountain.com/reference/get_api-serviceworkforce-locationgrouptrees-identifier.md): Find one locationGroupTree by its unique identifier.
- [find many locationGroupTrees](https://developer.fountain.com/reference/get_api-serviceworkforce-locationgrouptrees.md): Find many locationGroupTrees (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [delete one location](https://developer.fountain.com/reference/delete_api-serviceworkforce-locations-identifier.md): Delete one location
- [delete many locations](https://developer.fountain.com/reference/delete_api-serviceworkforce-locations.md): Delete many locations using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [Deletes a Location and its Company Attributes by its hireLocationUuid if they exist](https://developer.fountain.com/reference/delete_api-serviceworkforce-processes-locations-hirelocationuuid.md): Deletes a Location and its Company Attributes by its hireLocationUuid if they exist
- [count locations](https://developer.fountain.com/reference/get_api-serviceworkforce-locations-count.md): Count locations (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one location](https://developer.fountain.com/reference/get_api-serviceworkforce-locations-identifier.md): Find one location by its unique identifier.
- [find many locations](https://developer.fountain.com/reference/get_api-serviceworkforce-locations.md): Find many locations (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing location](https://developer.fountain.com/reference/patch_api-serviceworkforce-locations-identifier.md): Partially update one existing location
- [partially update many existing location](https://developer.fountain.com/reference/patch_api-serviceworkforce-locations.md): Partially update many existing location
- [Update multiple locations and replace their Company Attributes with the payload](https://developer.fountain.com/reference/patch_api-serviceworkforce-processes-locations-custom-attributes.md): Updates multiple Locations and upserts their Company Attributes. The provided customAttributesPayload replaces the entire set of attributes attached to each location: omit the field to leave existing attributes unchanged; provide an empty array ([]) to remove all attributes from the location. Values must match the attribute data type configured for the company attribute.
- [Update a location and replace its Company Attributes with the payload](https://developer.fountain.com/reference/patch_api-serviceworkforce-processes-locations-locationuuid-custom-attributes.md): Updates a Location and upserts its Company Attributes. The provided customAttributesPayload replaces the entire set of attributes attached to the location: omit the field to leave existing attributes unchanged; provide an empty array ([]) to remove all attributes from the location. Values must match the attribute data type configured for the company attribute.
- [create one or multiple locations](https://developer.fountain.com/reference/post_api-serviceworkforce-locations.md): Create one or multiple locations
- [Create a location and replace its Company Attributes with the payload](https://developer.fountain.com/reference/post_api-serviceworkforce-processes-locations-custom-attributes.md): Creates a Location and upserts its Company Attributes in one request. The provided customAttributesPayload replaces the entire set of attributes attached to the location: omit the field to create the location without company attributes; provide an empty array ([]) to create the location with no attributes. Values must match the attribute data type configured for the company attribute.
- [replace one location which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-locations-identifier.md): Replace one location which exists or not
- [replace many locations which exists or not](https://developer.fountain.com/reference/put_api-serviceworkforce-locations.md): Replace many locations which exists or not
- [count logNotes](https://developer.fountain.com/reference/get_api-serviceemployment-lognotes-count.md): Count logNotes (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one logNote](https://developer.fountain.com/reference/get_api-serviceemployment-lognotes-identifier.md): Find one logNote by its unique identifier.
- [find many logNotes](https://developer.fountain.com/reference/get_api-serviceemployment-lognotes.md): Find many logNotes (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [count openings](https://developer.fountain.com/reference/get_api-serviceworkforce-openings-count.md): Count openings (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one opening](https://developer.fountain.com/reference/get_api-serviceworkforce-openings-identifier.md): Find one opening by its unique identifier.
- [find many openings](https://developer.fountain.com/reference/get_api-serviceworkforce-openings.md): Find many openings (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [count opensignups](https://developer.fountain.com/reference/get_api-servicesecurity-opensignups-count.md): Count opensignups (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one opensignup](https://developer.fountain.com/reference/get_api-servicesecurity-opensignups-identifier.md): Find one opensignup by its unique identifier.
- [find many opensignups](https://developer.fountain.com/reference/get_api-servicesecurity-opensignups.md): Find many opensignups (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing opensignup](https://developer.fountain.com/reference/patch_api-servicesecurity-opensignups-identifier.md): Partially update one existing opensignup
- [partially update many existing opensignup](https://developer.fountain.com/reference/patch_api-servicesecurity-opensignups.md): Partially update many existing opensignup
- [create one or multiple opensignups](https://developer.fountain.com/reference/post_api-servicesecurity-opensignups.md): Create one or multiple opensignups
- [One stop setup for PAPI](https://developer.fountain.com/reference/post_api-servicesecurity-processes-papi-setup-v1-hireaccountuuid.md)
- [count participants](https://developer.fountain.com/reference/get_api-servicepulse-participants-count.md): Count participants (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one participant](https://developer.fountain.com/reference/get_api-servicepulse-participants-identifier.md): Find one participant by its unique identifier.
- [find many participants](https://developer.fountain.com/reference/get_api-servicepulse-participants.md): Find many participants (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Retrieve an assigned partner task](https://developer.fountain.com/reference/get_api-servicetodo-processes-partnertasks-assignedtaskuuid.md)
- [Add a new partner event to an assigned partner task](https://developer.fountain.com/reference/post_api-servicetodo-processes-partnertasks-assignedtaskuuid.md)
- [Get dashboard pending tasks summary](https://developer.fountain.com/reference/get_api-servicetodo-processes-dashboard-pending-tasks-summary.md)
- [delete one pulseSettings](https://developer.fountain.com/reference/delete_api-servicepulse-pulsesettings-identifier.md): Delete one pulseSettings
- [delete many pulseSettings](https://developer.fountain.com/reference/delete_api-servicepulse-pulsesettings.md): Delete many pulseSettings using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count pulseSettings](https://developer.fountain.com/reference/get_api-servicepulse-pulsesettings-count.md): Count pulseSettings (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one pulseSettings](https://developer.fountain.com/reference/get_api-servicepulse-pulsesettings-identifier.md): Find one pulseSettings by its unique identifier.
- [find many pulseSettings](https://developer.fountain.com/reference/get_api-servicepulse-pulsesettings.md): Find many pulseSettings (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing pulseSettings](https://developer.fountain.com/reference/patch_api-servicepulse-pulsesettings-identifier.md): Partially update one existing pulseSettings
- [partially update many existing pulseSettings](https://developer.fountain.com/reference/patch_api-servicepulse-pulsesettings.md): Partially update many existing pulseSettings
- [create one or multiple pulseSettings](https://developer.fountain.com/reference/post_api-servicepulse-pulsesettings.md): Create one or multiple pulseSettings
- [delete one questionBank](https://developer.fountain.com/reference/delete_api-servicepulse-questionbanks-identifier.md): Delete one questionBank
- [delete many questionBanks](https://developer.fountain.com/reference/delete_api-servicepulse-questionbanks.md): Delete many questionBanks using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count questionBanks](https://developer.fountain.com/reference/get_api-servicepulse-questionbanks-count.md): Count questionBanks (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one questionBank](https://developer.fountain.com/reference/get_api-servicepulse-questionbanks-identifier.md): Find one questionBank by its unique identifier.
- [find many questionBanks](https://developer.fountain.com/reference/get_api-servicepulse-questionbanks.md): Find many questionBanks (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing questionBank](https://developer.fountain.com/reference/patch_api-servicepulse-questionbanks-identifier.md): Partially update one existing questionBank
- [partially update many existing questionBank](https://developer.fountain.com/reference/patch_api-servicepulse-questionbanks.md): Partially update many existing questionBank
- [create one or multiple questionBanks](https://developer.fountain.com/reference/post_api-servicepulse-questionbanks.md): Create one or multiple questionBanks
- [delete one referralCampaign](https://developer.fountain.com/reference/delete_api-servicereferral-referralcampaigns-identifier.md): Delete one referralCampaign
- [delete many referralCampaigns](https://developer.fountain.com/reference/delete_api-servicereferral-referralcampaigns.md): Delete many referralCampaigns using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [retrieve a list of Hire openings with targeting](https://developer.fountain.com/reference/get_api-servicereferral-processes-referralcampaigns-companyuuid-openings.md)
- [count referralCampaigns](https://developer.fountain.com/reference/get_api-servicereferral-referralcampaigns-count.md): Count referralCampaigns (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one referralCampaign](https://developer.fountain.com/reference/get_api-servicereferral-referralcampaigns-identifier.md): Find one referralCampaign by its unique identifier.
- [find many referralCampaigns](https://developer.fountain.com/reference/get_api-servicereferral-referralcampaigns.md): Find many referralCampaigns (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing referralCampaign](https://developer.fountain.com/reference/patch_api-servicereferral-referralcampaigns-identifier.md): Partially update one existing referralCampaign
- [partially update many existing referralCampaign](https://developer.fountain.com/reference/patch_api-servicereferral-referralcampaigns.md): Partially update many existing referralCampaign
- [Process a referral campaign request](https://developer.fountain.com/reference/post_api-servicereferral-processes-referralcampaigns.md)
- [create one or multiple referralCampaigns](https://developer.fountain.com/reference/post_api-servicereferral-referralcampaigns.md): Create one or multiple referralCampaigns
- [replace one referralCampaign which exists or not](https://developer.fountain.com/reference/put_api-servicereferral-referralcampaigns-identifier.md): Replace one referralCampaign which exists or not
- [replace many referralCampaigns which exists or not](https://developer.fountain.com/reference/put_api-servicereferral-referralcampaigns.md): Replace many referralCampaigns which exists or not
- [Get referral setting by company UUID (public)](https://developer.fountain.com/reference/get_api-servicereferral-processes-referralsettings-companyuuid.md): Returns referral setting for a company, public endpoint for referral workers
- [Initialize referral setting](https://developer.fountain.com/reference/post_api-servicereferral-processes-referralsettings-initialize-companyuuid.md)
- [Retreive a requirement by its unique identifier](https://developer.fountain.com/reference/get_api-servicecompliancev2-requirements-identifier.md)
- [List requirements](https://developer.fountain.com/reference/get_api-servicecompliancev2-requirements.md)
- [Create one or multiple requirements](https://developer.fountain.com/reference/post_api-servicecompliancev2-requirements.md)
- [Find and update a requirement](https://developer.fountain.com/reference/put_api-servicecompliancev2-requirements-identifier.md): Partially update one existing requirement
- [/api/serviceattendance/processes/shifts/{shiftUuid}](https://developer.fountain.com/reference/delete_api-serviceattendance-processes-shifts-shiftuuid.md)
- [count shifts](https://developer.fountain.com/reference/get_api-serviceattendance-shifts-count.md): Count shifts (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one shift](https://developer.fountain.com/reference/get_api-serviceattendance-shifts-identifier.md): Find one shift by its unique identifier.
- [find many shifts](https://developer.fountain.com/reference/get_api-serviceattendance-shifts.md): Find many shifts (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Update shifts, validated by rules. Fails with a 409 if there are any blockers. Note: When adding breaks use v4 uuid.](https://developer.fountain.com/reference/patch_api-serviceattendance-processes-shifts.md)
- [/api/serviceattendance/processes/shifts/{locationUuid}/publish](https://developer.fountain.com/reference/post_api-serviceattendance-processes-shifts-locationuuid-publish.md)
- [Publish an individual shift](https://developer.fountain.com/reference/post_api-serviceattendance-processes-shifts-shiftuuid-publishsingleshift.md)
- [/api/serviceattendance/processes/shifts/{shiftUuid}/resetNextVersion](https://developer.fountain.com/reference/post_api-serviceattendance-processes-shifts-shiftuuid-resetnextversion.md)
- [create one or multiple shifts](https://developer.fountain.com/reference/post_api-serviceattendance-shifts.md): Create one or multiple shifts
- [Delete multiple shifts](https://developer.fountain.com/reference/delete_api-serviceattendance-processes-shifts-deleteshifts.md)
- [Publish multiple shifts](https://developer.fountain.com/reference/post_api-serviceattendance-processes-shifts-publishshifts.md)
- [delete one shiftTag](https://developer.fountain.com/reference/delete_api-serviceattendance-shifttags-identifier.md): Delete one shiftTag
- [delete many shiftTags](https://developer.fountain.com/reference/delete_api-serviceattendance-shifttags.md): Delete many shiftTags using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count shiftTags](https://developer.fountain.com/reference/get_api-serviceattendance-shifttags-count.md): Count shiftTags (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one shiftTag](https://developer.fountain.com/reference/get_api-serviceattendance-shifttags-identifier.md): Find one shiftTag by its unique identifier.
- [find many shiftTags](https://developer.fountain.com/reference/get_api-serviceattendance-shifttags.md): Find many shiftTags (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing shiftTag](https://developer.fountain.com/reference/patch_api-serviceattendance-shifttags-identifier.md): Partially update one existing shiftTag
- [partially update many existing shiftTag](https://developer.fountain.com/reference/patch_api-serviceattendance-shifttags.md): Partially update many existing shiftTag
- [create one or multiple shiftTags](https://developer.fountain.com/reference/post_api-serviceattendance-shifttags.md): Create one or multiple shiftTags
- [Return the attachment of a signatureRequest as a buffer](https://developer.fountain.com/reference/get_api-servicemedia-processes-signaturerequests-signaturerequestidentifier-attachment.md)
- [Retrieve a link or download files linked to a signatureRequest document](https://developer.fountain.com/reference/get_api-servicemedia-processes-signaturerequests-signaturerequestidentifier-files.md)
- [count signDocs](https://developer.fountain.com/reference/get_api-servicemedia-signdocs-count.md): Count signDocs (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one signDoc](https://developer.fountain.com/reference/get_api-servicemedia-signdocs-identifier.md): Find one signDoc by its unique identifier.
- [find many signDocs](https://developer.fountain.com/reference/get_api-servicemedia-signdocs.md): Find many signDocs (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Delete an employer with slot reassignment](https://developer.fountain.com/reference/delete_api-servicestaff-employers-identifier-withreassignment.md): Delete an employer from the system and reassign their active slots to another user.
- [delete one storedFile](https://developer.fountain.com/reference/delete_api-servicemedia-storedfiles-identifier.md): Delete one storedFile
- [delete many storedFiles](https://developer.fountain.com/reference/delete_api-servicemedia-storedfiles.md): Delete many storedFiles using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [generate a signed file url to access a file](https://developer.fountain.com/reference/get_api-servicemedia-processes-company-companyidentifier-storedfiles-storedfileidentifier-url.md): Generate a signed stored file url to access the file
- [Count files from CSV imports storage folder only](https://developer.fountain.com/reference/get_api-servicemedia-processes-files-csvimports-count.md): Count files from CSV imports storage folder only
- [List files from CSV imports storage folder only](https://developer.fountain.com/reference/get_api-servicemedia-processes-files-csvimports.md): List files from CSV imports storage folder only
- [count storedFiles](https://developer.fountain.com/reference/get_api-servicemedia-storedfiles-count.md): Count storedFiles (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one storedFile](https://developer.fountain.com/reference/get_api-servicemedia-storedfiles-identifier.md): Find one storedFile by its unique identifier.
- [find many storedFiles](https://developer.fountain.com/reference/get_api-servicemedia-storedfiles.md): Find many storedFiles (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing storedFile](https://developer.fountain.com/reference/patch_api-servicemedia-storedfiles-identifier.md): Partially update one existing storedFile
- [partially update many existing storedFile](https://developer.fountain.com/reference/patch_api-servicemedia-storedfiles.md): Partially update many existing storedFile
- [Create a file and get an upload presigned URL for an object storage in the attachments bucket](https://developer.fountain.com/reference/post_api-servicemedia-processes-files-attachment.md)
- [Create a file and get an upload presigned URL for an object storage in the csv imports bucket](https://developer.fountain.com/reference/post_api-servicemedia-processes-files-csvimports.md)
- [Create a file and get an upload presigned URL for an object storage in the edm bucket](https://developer.fountain.com/reference/post_api-servicemedia-processes-files-edm.md)
- [Upload one or two files from a publicly accessible URL to our object storage. The combined file must not exceed 15MB.](https://developer.fountain.com/reference/post_api-servicemedia-processes-files-storagefolder-url-upload.md)
- [delete one survey](https://developer.fountain.com/reference/delete_api-servicepulse-surveys-identifier.md): Delete one survey
- [delete many surveys](https://developer.fountain.com/reference/delete_api-servicepulse-surveys.md): Delete many surveys using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count surveys](https://developer.fountain.com/reference/get_api-servicepulse-surveys-count.md): Count surveys (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one survey](https://developer.fountain.com/reference/get_api-servicepulse-surveys-identifier.md): Find one survey by its unique identifier.
- [find many surveys](https://developer.fountain.com/reference/get_api-servicepulse-surveys.md): Find many surveys (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing survey](https://developer.fountain.com/reference/patch_api-servicepulse-surveys-identifier.md): Partially update one existing survey
- [partially update many existing survey](https://developer.fountain.com/reference/patch_api-servicepulse-surveys.md): Partially update many existing survey
- [create one or multiple surveys](https://developer.fountain.com/reference/post_api-servicepulse-surveys.md): Create one or multiple surveys
- [delete one tag](https://developer.fountain.com/reference/delete_api-serviceemployment-tags-identifier.md): Delete one tag
- [delete many tags](https://developer.fountain.com/reference/delete_api-serviceemployment-tags.md): Delete many tags using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count tags](https://developer.fountain.com/reference/get_api-serviceemployment-tags-count.md): Count tags (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one tag](https://developer.fountain.com/reference/get_api-serviceemployment-tags-identifier.md): Find one tag by its unique identifier.
- [find many tags](https://developer.fountain.com/reference/get_api-serviceemployment-tags.md): Find many tags (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing tag](https://developer.fountain.com/reference/patch_api-serviceemployment-tags-identifier.md): Partially update one existing tag
- [partially update many existing tag](https://developer.fountain.com/reference/patch_api-serviceemployment-tags.md): Partially update many existing tag
- [create one or multiple tags](https://developer.fountain.com/reference/post_api-serviceemployment-tags.md): Create one or multiple tags
- [Count talent](https://developer.fountain.com/reference/get_api-servicepool-talents-count.md): Counts visible talent only by default (isHidden is not true and archivedAt does not exist). Pass onlyReturnHiddenTalent=true to count only hidden talent instead.
- [Count audience campaigns the talent has ever been part of (filterable)](https://developer.fountain.com/reference/get_api-servicepool-talents-identifier-audiencecampaigns-count.md)
- [Get audience campaigns for a talent](https://developer.fountain.com/reference/get_api-servicepool-talents-identifier-audiencecampaigns.md)
- [Count audiences in a talent history (filterable by lastEventType)](https://developer.fountain.com/reference/get_api-servicepool-talents-identifier-audiencehistory-count.md)
- [Get audience history grouped by audience for a talent](https://developer.fountain.com/reference/get_api-servicepool-talents-identifier-audiencehistory.md): Returns one entry per audience the talent has interacted with. Each entry includes the full event history trail (entered/exited with reasons), the linked campaigns (name, status, type), and a `lastEventType` denormalized from the most recent event. To scope results, filter on `lastEventType` via the standard filter syntax — e.g. `filter[where][lastEventType][$in][]=entered` (or `exited`, or both). The match runs after the audience-level grouping. Supported filter fields: `lastEventType` (string/`$in`), `audienceName` (regex), and `relatedCampaigns.name` (regex).
- [Retrieve a talent by its unique identifier](https://developer.fountain.com/reference/get_api-servicepool-talents-identifier.md)
- [Fetch all template attributes available for talents](https://developer.fountain.com/reference/get_api-servicepool-talents-templateattributes.md): Returns all template attributes available for talent-based templates: custom attributes (from talents primaryCustomValues), talent base attributes, and company/brand attributes. This is the single source of truth for template variable resolution used by both the frontend editor and Cue.
- [fetch list of talent](https://developer.fountain.com/reference/get_api-servicepool-talents.md): Returns visible talent only by default (isHidden is not true and archivedAt does not exist). Pass onlyReturnHiddenTalent=true to return only hidden talent instead.
- [Update one or multiple talent](https://developer.fountain.com/reference/patch_api-servicepool-talents.md): Partially update multiple existing talents
- [Create one or multiple talent](https://developer.fountain.com/reference/post_api-servicepool-talents.md)
- [Find and update a talent](https://developer.fountain.com/reference/put_api-servicepool-talents-identifier.md): Partially update one existing talent
- [Delete a Test task flow for copilot](https://developer.fountain.com/reference/delete_api-servicetodo-processes-taskflows-taskflowidentifier-forcopilot.md)
- [delete one taskFlow](https://developer.fountain.com/reference/delete_api-servicetodo-taskflows-identifier.md): Delete one taskFlow
- [delete many taskFlows](https://developer.fountain.com/reference/delete_api-servicetodo-taskflows.md): Delete many taskFlows using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [Check if a calendar group is used by any task flows](https://developer.fountain.com/reference/get_api-servicetodo-processes-taskflows-checkcalendargroupusage.md)
- [Retrieve all workers of a taskFlow with data such as completion rate of tasks](https://developer.fountain.com/reference/get_api-servicetodo-processes-taskflows-taskflowidentifier-workers-processed.md)
- [Retrieve all information about one worker and its taskFlow completion](https://developer.fountain.com/reference/get_api-servicetodo-processes-taskflows-taskflowidentifier-workers-workeridentifier-processed.md)
- [Retrieve all taskFlows for a given worker with data such as completion rate of tasks](https://developer.fountain.com/reference/get_api-servicetodo-processes-taskflows-workers-workeridentifier-processed.md)
- [count taskFlows](https://developer.fountain.com/reference/get_api-servicetodo-taskflows-count.md): Count taskFlows (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one taskFlow](https://developer.fountain.com/reference/get_api-servicetodo-taskflows-identifier.md): Find one taskFlow by its unique identifier.
- [find many taskFlows](https://developer.fountain.com/reference/get_api-servicetodo-taskflows.md): Find many taskFlows (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing taskFlow](https://developer.fountain.com/reference/patch_api-servicetodo-taskflows-identifier.md): Partially update one existing taskFlow
- [partially update many existing taskFlow](https://developer.fountain.com/reference/patch_api-servicetodo-taskflows.md): Partially update many existing taskFlow
- [Apply Test task flow changes back to its source draft](https://developer.fountain.com/reference/post_api-servicetodo-processes-taskflows-applytestchangestodraftforcopilot.md)
- [clone task flow(s)](https://developer.fountain.com/reference/post_api-servicetodo-processes-taskflows-clone.md)
- [Clone a draft task flow as a Test flow for copilot](https://developer.fountain.com/reference/post_api-servicetodo-processes-taskflows-cloneforcopilot.md)
- [Create task flow for copilot](https://developer.fountain.com/reference/post_api-servicetodo-processes-taskflows-createforcopilot.md)
- [Publish a Test task flow for copilot](https://developer.fountain.com/reference/post_api-servicetodo-processes-taskflows-taskflowidentifier-publishforcopilot.md)
- [create one or multiple taskFlows](https://developer.fountain.com/reference/post_api-servicetodo-taskflows.md): Create one or multiple taskFlows
- [delete one task](https://developer.fountain.com/reference/delete_api-servicetodo-tasks-identifier.md): Delete one task
- [delete many tasks](https://developer.fountain.com/reference/delete_api-servicetodo-tasks.md): Delete many tasks using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count tasks](https://developer.fountain.com/reference/get_api-servicetodo-tasks-count.md): Count tasks (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one task](https://developer.fountain.com/reference/get_api-servicetodo-tasks-identifier.md): Find one task by its unique identifier.
- [find many tasks](https://developer.fountain.com/reference/get_api-servicetodo-tasks.md): Find many tasks (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing task](https://developer.fountain.com/reference/patch_api-servicetodo-tasks-identifier.md): Partially update one existing task
- [partially update many existing task](https://developer.fountain.com/reference/patch_api-servicetodo-tasks.md): Partially update many existing task
- [create one or multiple tasks](https://developer.fountain.com/reference/post_api-servicetodo-tasks.md): Create one or multiple tasks
- [delete one theme](https://developer.fountain.com/reference/delete_api-servicepulse-themes-identifier.md): Delete one theme
- [delete many themes](https://developer.fountain.com/reference/delete_api-servicepulse-themes.md): Delete many themes using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [count themes](https://developer.fountain.com/reference/get_api-servicepulse-themes-count.md): Count themes (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one theme](https://developer.fountain.com/reference/get_api-servicepulse-themes-identifier.md): Find one theme by its unique identifier.
- [find many themes](https://developer.fountain.com/reference/get_api-servicepulse-themes.md): Find many themes (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing theme](https://developer.fountain.com/reference/patch_api-servicepulse-themes-identifier.md): Partially update one existing theme
- [partially update many existing theme](https://developer.fountain.com/reference/patch_api-servicepulse-themes.md): Partially update many existing theme
- [create one or multiple themes](https://developer.fountain.com/reference/post_api-servicepulse-themes.md): Create one or multiple themes
- [Delete time-off](https://developer.fountain.com/reference/delete_api-serviceattendance-processes-timeoff-timeoffuuid.md)
- [count timeOff](https://developer.fountain.com/reference/get_api-serviceattendance-timeoff-count.md): Count timeOff (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one timeOff](https://developer.fountain.com/reference/get_api-serviceattendance-timeoff-identifier.md): Find one timeOff by its unique identifier.
- [find many timeOff](https://developer.fountain.com/reference/get_api-serviceattendance-timeoff.md): Find many timeOff (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [/api/serviceattendance/processes/timeOff/{timeOffUuid}](https://developer.fountain.com/reference/patch_api-serviceattendance-processes-timeoff-timeoffuuid.md)
- [/api/serviceattendance/processes/timeOff](https://developer.fountain.com/reference/post_api-serviceattendance-processes-timeoff.md)
- [count timesheets](https://developer.fountain.com/reference/get_api-serviceattendance-timesheets-count.md): Count timesheets (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one timesheet](https://developer.fountain.com/reference/get_api-serviceattendance-timesheets-identifier.md): Find one timesheet by its unique identifier.
- [find many timesheets](https://developer.fountain.com/reference/get_api-serviceattendance-timesheets.md): Find many timesheets (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [/api/serviceattendance/processes/timesheets/{timesheetUuid}/addClockEvent](https://developer.fountain.com/reference/patch_api-serviceattendance-processes-timesheets-timesheetuuid-addclockevent.md)
- [partially update one existing timesheet](https://developer.fountain.com/reference/patch_api-serviceattendance-timesheets-identifier.md): Partially update one existing timesheet
- [partially update many existing timesheet](https://developer.fountain.com/reference/patch_api-serviceattendance-timesheets.md): Partially update many existing timesheet
- [Returns exported headers, rows, filename for timesheets. Specify target timesheets by uuid or by filter](https://developer.fountain.com/reference/post_api-serviceattendance-processes-timesheets-export.md)
- [Exports timesheets to the preconfigured payroll webhook integration](https://developer.fountain.com/reference/post_api-serviceattendance-processes-timesheets-exportviaapi.md)
- [Returns exported headers, rows, filename for timesheets. Specify target timesheets by uuid or by filter](https://developer.fountain.com/reference/post_api-serviceattendance-processes-timesheets-getexportabletimesheets.md)
- [Marks a timesheet as deleted and cancels scheduled events](https://developer.fountain.com/reference/post_api-serviceattendance-processes-timesheets-markdeleted.md)
- [create one or multiple timesheets](https://developer.fountain.com/reference/post_api-serviceattendance-timesheets.md): Create one or multiple timesheets
- [Get counts of workers with tasks in different statuses](https://developer.fountain.com/reference/get_api-servicetodo-processes-workers-metrics-count.md)
- [Api endpoint to get workers by start date](https://developer.fountain.com/reference/get_api-servicetodo-processes-workers-startsbydate.md)
- [Get partner status with partnerStatus](https://developer.fountain.com/reference/get_api-servicetodo-processes-workers-workeridentifier-partneronboardstatus.md)
- [Get worker task flows](https://developer.fountain.com/reference/get_api-servicetodo-processes-workers-workeridentifier-taskflows.md)
- [Reprocess worker onboarding](https://developer.fountain.com/reference/post_api-servicetodo-processes-workers-workeridentifier-reprocess.md): Reprocesses a worker's onboarding by refreshing segments, archiving/assigning tasks, updating overall status, checking completion, and reconciling Todo Notifications V2 scheduled reminders/deadlines for eligible workers. Useful for fixing issues with task flow assignments, status calculations, or scheduled notification state.
- [Delete a unified job](https://developer.fountain.com/reference/delete_api-servicepool-unifiedjobs-identifier.md)
- [Find unifiedJobs matches for a given talent based on aggregate vector match](https://developer.fountain.com/reference/get_api-servicepool-talents-identifier-jobmatches.md)
- [Count unifiedJobs](https://developer.fountain.com/reference/get_api-servicepool-unifiedjobs-count.md)
- [Retrieve a unified job by its unique identifier](https://developer.fountain.com/reference/get_api-servicepool-unifiedjobs-identifier.md)
- [fetch list of unified jobs](https://developer.fountain.com/reference/get_api-servicepool-unifiedjobs.md)
- [Create one or multiple unified jobs](https://developer.fountain.com/reference/post_api-servicepool-unifiedjobs.md)
- [Find and update a unified job](https://developer.fountain.com/reference/put_api-servicepool-unifiedjobs-identifier.md): Partially update one existing unified job
- [Provides the new applicants metric for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-metrics-applicants-new.md)
- [Provides the applicants pipeline metric for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-metrics-applicants-pipeline.md)
- [Provides the mark attendance task metric for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-metrics-markattendance.md)
- [Provides the respond to messages task metric for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-metrics-respondtomessages.md)
- [Provides the review applicants task metric for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-metrics-reviewapplicants.md)
- [Provides the review files task metric for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-metrics-reviewfiles.md)
- [Provides a list of openings for a current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-openings.md)
- [Provides a list of schedule events for the current employer user](https://developer.fountain.com/reference/get_api-servicetodo-processes-universal-dashboard-schedule-events.md)
- [Retrieve a short-lived authenticated URL for a worker's portal](https://developer.fountain.com/reference/get_api-servicesecurity-processes-workers-workeruuid-impersonate.md): Impersonate a user in their own portal.
- [Retrieve a short-lived authenticated URL for a worker's portal](https://developer.fountain.com/reference/get_api-servicesecurity-processes-employers-employeruuid-impersonate.md): Impersonate a user in their own portal.
- [count viewEmploymentProfiles](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-all-count.md): Count viewEmploymentProfiles (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one viewEmploymentProfile](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-all-workers-workeridentifier.md): Find one viewEmploymentProfile by its unique identifier.
- [find many viewEmploymentProfiles](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-all.md): Find many viewEmploymentProfiles (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Retrieve a submission file](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-i9-workers-workeridentifier-submission-submissionid-attachments-file.md)
- [Retrieve a submission file](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-i9-workers-workeridentifier-submission-submissionid-file.md)
- [Sync viewEmploymentProfile and Partner resources for a given worker](https://developer.fountain.com/reference/post_api-serviceemployment-processes-companies-companyidentifier-profiles-all-workers-workeridentifier-sync.md)
- [count viewEmploymentProfilesI9](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-i9-count.md): Count viewEmploymentProfilesI9 (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one viewEmploymentProfileI9](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-i9-workers-workeridentifier.md): Find one viewEmploymentProfileI9 by its unique identifier.
- [find many viewEmploymentProfilesI9](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-i9.md): Find many viewEmploymentProfilesI9 (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [count viewEmploymentProfilesW4](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-w4-count.md): Count viewEmploymentProfilesW4 (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one viewEmploymentProfileW4](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-w4-workers-workeridentifier.md): Find one viewEmploymentProfileW4 by its unique identifier.
- [find many viewEmploymentProfilesW4](https://developer.fountain.com/reference/get_api-serviceemployment-processes-profiles-w4.md): Find many viewEmploymentProfilesW4 (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [count w4Profiles](https://developer.fountain.com/reference/get_api-servicetodo-w4profiles-count.md): Count w4Profiles (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one w4Profile](https://developer.fountain.com/reference/get_api-servicetodo-w4profiles-identifier.md): Find one w4Profile by its unique identifier.
- [find many w4Profiles](https://developer.fountain.com/reference/get_api-servicetodo-w4profiles.md): Find many w4Profiles (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Retrieve the workerComplianceProfile for an authenticated worker](https://developer.fountain.com/reference/get_api-servicecompliancev2-workercomplianceprofile-worker-workeridentifier.md)
- [Retreive a workerComplianceProfile by its unique identifier](https://developer.fountain.com/reference/get_api-servicecompliancev2-workercomplianceprofiles-identifier.md)
- [List workerComplianceProfiles](https://developer.fountain.com/reference/get_api-servicecompliancev2-workercomplianceprofiles.md)
- [Search workerComplianceProfiles (Atlas Search)](https://developer.fountain.com/reference/post_api-servicecompliancev2-workercomplianceprofiles-search.md)
- [Create a worker request rule and associate it with a location or location group](https://developer.fountain.com/reference/post_api-serviceattendance-processes-workerrequestrules-createandassociate.md)
- [Delete one or more worker request rules](https://developer.fountain.com/reference/post_api-serviceattendance-processes-workerrequestrules-deleteanddisassociate.md)
- [count workerRequests](https://developer.fountain.com/reference/get_api-serviceattendance-workerrequests-count.md): Count workerRequests (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one workerRequest](https://developer.fountain.com/reference/get_api-serviceattendance-workerrequests-identifier.md): Find one workerRequest by its unique identifier.
- [find many workerRequests](https://developer.fountain.com/reference/get_api-serviceattendance-workerrequests.md): Find many workerRequests (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [Delete a worker custom attribute](https://developer.fountain.com/reference/delete_api-serviceworkforce-processes-workers-workeridentifier-customattributes-customattributeidentifier.md)
- [delete one worker](https://developer.fountain.com/reference/delete_api-serviceworkforce-workers-identifier.md): Delete one worker
- [delete many workers](https://developer.fountain.com/reference/delete_api-serviceworkforce-workers.md): Delete many workers using filtering. You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [Get the worker profile without sensitive filters](https://developer.fountain.com/reference/get_api-serviceworkforce-processes-workers-workeridentifier-sensitiveworkerdata.md)
- [count workers](https://developer.fountain.com/reference/get_api-serviceworkforce-workers-count.md): Count workers (with filtering, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25
- [find one worker](https://developer.fountain.com/reference/get_api-serviceworkforce-workers-identifier.md): Find one worker by its unique identifier.
- [find many workers](https://developer.fountain.com/reference/get_api-serviceworkforce-workers.md): Find many workers (with filtering, projection, pagination and limiting). You can use filters in the query parameters (properly URL encoded) to restrict the search results: - To restrict the search to specific values for a given field name, you can use the following syntax: filter[where][fieldName][eq]=value. Note that you can also nest the filter object to filter on multiple fields, like so: filter[where][and][0][fieldName1][eq]=value1&filter[where][and][1][fieldName2][eq]=value2. You can also use operators like gt, gte, lt, lte, ne, in, nin, etc. - To limit the number of results returned by the query, use the following syntax: filter[limit]=25&filter[skip]=25 - To only return specific fields, use the projection query parameter. Usage is as follows: filter[fields][fieldName1]=true&filter[fields][fieldName2]=true.
- [partially update one existing worker](https://developer.fountain.com/reference/patch_api-serviceworkforce-workers-identifier.md): Partially update one existing worker
- [partially update many existing worker](https://developer.fountain.com/reference/patch_api-serviceworkforce-workers.md): Partially update many existing worker
- [message one or many workers](https://developer.fountain.com/reference/post_api-serviceworkforce-processes-workers-sendworkermessage.md)
- [Terminate a worker access](https://developer.fountain.com/reference/post_api-serviceworkforce-processes-workers-workeridentifier-terminate.md)
- [create one or multiple workers](https://developer.fountain.com/reference/post_api-serviceworkforce-workers.md): Create one or multiple workers
- [Create or update a worker custom attribute value](https://developer.fountain.com/reference/put_api-serviceworkforce-processes-workers-workeridentifier-customattributes-customattributeidentifier.md)
- [Create or update a worker's custom attributes values](https://developer.fountain.com/reference/put_api-serviceworkforce-processes-workers-workeridentifier-customattributes.md)
- [Query Yardstik for the full list of account packages associated with the account defined by the API key](https://developer.fountain.com/reference/get_api-servicetodo-processes-yardstick-packages.md)