> ## Documentation Index > Fetch the complete documentation index at: https://developer.instantly.ai/llms.txt > Use this file to discover all available pages before exploring further. # Bulk assign leads to organization users > Bulk assign leads to organization users ## OpenAPI ````yaml https://api.instantly.ai/openapi/api_v2.json post /api/v2/leads/bulk-assign openapi: 3.1.0 info: title: API Explorer description: >- The entire API V2 documentation is interactive and can be tested here. To the right side of every endpoint you will see a box with an example request. You can click on the "Try it" button to send a request to the server right from the docs. You will need to provide an API key by clicking the `ApiKeyAuth_token` blue text. version: 2.0.0 servers: - url: https://api.instantly.ai description: Instantly API Server security: - ApiKeyAuth: [] tags: - name: Analytics description: Endpoints related to analytics x-displayName: Analytics - name: OAuth description: >- OAuth authentication endpoints for connecting Google and Microsoft email accounts x-displayName: OAuth - name: Account description: An email account that can be used to send campaigns x-displayName: Account - name: Campaign description: A campaign that can be sent to a list of recipients x-displayName: Campaign - name: Email description: >- A campaign email, a reply, a manually sent email, or any other email that's visible in the Unibox x-displayName: Email - name: EmailVerification description: A single email verification x-displayName: Email Verification - name: LeadList description: A list used to store leads x-displayName: Lead List - name: InboxPlacementTest description: An inbox placement test x-displayName: Inbox Placement Test - name: InboxPlacementAnalytics description: Analytics data for individual emails in inbox placement tests x-displayName: Inbox Placement Analytics - name: InboxPlacementBlacklist&SpamAssassinReport description: Report data for an inbox placement test x-displayName: Inbox Placement Blacklist & SpamAssassin Report - name: APIKey description: API Key x-displayName: API Key - name: AccountCampaignMapping description: Account Campaign Mapping x-displayName: Account Campaign Mapping - name: Lead description: A lead entity representing an individual lead x-displayName: Lead - name: BackgroundJob description: A background job that can be used to perform long-running tasks x-displayName: Background Job - name: CustomTag description: >- A custom tag for organizing and categorizing accounts and campaigns. You can use them as filters in apis that list accounts and campaigns. x-displayName: Custom Tag - name: CustomTagMapping description: >- This entity represents a tag being assigned to a specific campaign or email account. When an email account is assigned a tag, a new custom tag mapping entry is created, which connects the tag (`tag_id` field) with the email account (`resource_id` field). You can use it to see which tag si connected to which resource. x-displayName: Custom Tag Mapping - name: BlockListEntry description: A blocked email or domain x-displayName: Block List Entry - name: LeadLabel description: A custom label for categorizing and managing leads x-displayName: Lead Label - name: Workspace description: A workspace entity representing a workspace x-displayName: Workspace - name: SuperSearchEnrichment description: >- An enrichment can take different forms, such as email enrichment or LinkedIn enrichment. Leads may be imported from SuperSearch using the dedicated endpoint, or enriched directly within a list or campaign by attaching an enrichment to it. x-displayName: SuperSearch Enrichment - name: WorkspaceGroupMember description: >- A member of a workspace group. You can use the endpoints within this entity to manage the members of a workspace group. x-displayName: Workspace Group Member - name: WorkspaceMember description: A member of a workspace with associated user details x-displayName: Workspace Member - name: CampaignSubsequence description: A subsequence entity representing a follow-up sequence x-displayName: Campaign Subsequence - name: AuditLog description: Audit log records for tracking system activities x-displayName: Audit Log - name: Webhook description: A webhook subscription for receiving event notifications x-displayName: Webhook - name: WebhookEvent description: A webhook event that was sent or attempted to be sent x-displayName: Webhook Event - name: DFYEmailAccountOrder description: A Done-For-You email account order x-displayName: DFY Email Account Order - name: CustomPromptTemplate description: Custom prompt templates for creating custom prompts x-displayName: Custom Prompt Template - name: SalesFlow description: >- Manages how sales users view and interact with campaign and lead lists within the sales flow. x-displayName: Sales Flow - name: EmailTemplate description: A campaign email template x-displayName: Email Template - name: WorkspaceBilling description: Workspace Billing x-displayName: Workspace Billing - name: CRMActions description: CRM related actions x-displayName: CRM Actions paths: /api/v2/leads/bulk-assign: post: tags: - Lead summary: Bulk assign leads to organization users description: Bulk assign leads to organization users operationId: bulkAssignLeads requestBody: content: application/json: schema: type: object properties: search: type: string description: The search query to filter leads by. example: test filter: type: string enum: - FILTER_VAL_CONTACTED - FILTER_VAL_NOT_CONTACTED - FILTER_VAL_COMPLETED - FILTER_VAL_UNSUBSCRIBED - FILTER_VAL_ACTIVE - FILTER_LEAD_INTERESTED - FILTER_LEAD_NOT_INTERESTED - FILTER_LEAD_MEETING_BOOKED - FILTER_LEAD_MEETING_COMPLETED - FILTER_LEAD_CLOSED - FILTER_LEAD_OUT_OF_OFFICE - FILTER_LEAD_WRONG_PERSON - FILTER_LEAD_LOST - FILTER_LEAD_NO_SHOW - FILTER_LEAD_CUSTOM_LABEL_POSITIVE - FILTER_LEAD_CUSTOM_LABEL_NEGATIVE - FILTER_VAL_BOUNCED - FILTER_VAL_SKIPPED - FILTER_VAL_RISKY - FILTER_VAL_INVALID - FILTER_VAL_VALID - FILTER_VAL_IN_SUBSEQUENCE - FILTER_VAL_OPENED_NO_REPLY - FILTER_VAL_COMPLETED_NO_REPLY - FILTER_VAL_NO_OPENS - FILTER_VAL_REPLIED - FILTER_VAL_LINK_CLICKED description: The filter to apply to the leads. example: FILTER_LEAD_CLOSED campaign: type: string format: uuid description: The ID of the campaign to filter leads by. example: 019e18e2-a5e1-752d-a736-5daf6da90de8 list_id: type: string format: uuid description: The ID of the list to filter leads by. example: 019e18e2-a5e1-752d-a736-5db034bcd4c0 in_campaign: type: boolean description: Whether the leads are in the campaign. example: true in_list: type: boolean description: Whether the leads are in the list. example: true organization_user_ids: type: array items: type: string format: uuid example: 019e18e2-a5e1-752d-a736-5db13d4a09b2 minItems: 1 smart_view_id: type: string format: uuid description: The ID of the smart view to filter leads by. example: 019e18e2-a5e1-752d-a736-5db27e4c8cf6 ids: type: array items: type: string format: uuid example: 019e18e2-a5e1-752d-a736-5db3861230cd description: The IDs of the leads to filter by. limit: type: integer minimum: 0 description: The limit of the number of leads to return. example: 10 queries: type: array items: type: object properties: actionType: type: string enum: - reply - email-open - last-contacted - link-click - lead-status - lead-status-change x-enumDescriptions: reply: Reply email-open: Email Opened last-contacted: Last Contacted link-click: Link Click lead-status: Lead Status lead-status-change: Lead Status Change example: email-open values: type: object properties: occurrence-days: type: number example: 5 occurrence-count: type: object properties: condition: type: string enum: - more - less - equal x-enumDescriptions: more: More than the count less: Less than the count equal: Equal to the count example: more count: type: number example: 5 lead-status: type: object properties: status: type: number example: 5 condition: type: string enum: - is - is-not x-enumDescriptions: is: Is is-not: Is Not example: is required: - actionType - values required: - organization_user_ids required: true responses: '202': description: Default Response content: application/json: schema: type: object properties: status: type: string example: accepted message: type: string example: Your request will be processed in a background job '400': description: Default Response content: application/json: schema: type: object properties: message: type: string example: Invalid ID on `organization_user_ids` field '401': description: >- This request is unauthorized (either the Authorization header is missing or invalid, or the API key has been revoked) content: application/json: schema: type: object properties: statusCode: type: number enum: - 401 example: 401 error: type: string enum: - Unauthorized example: Unauthorized message: type: string example: Missing Authorization header required: - statusCode - error - message '402': description: >- This request cannot be fulfilled because the workspace does not have an active paid plan content: application/json: schema: type: object properties: statusCode: type: number enum: - 402 example: 402 error: type: string enum: - Payment Required example: Payment Required message: type: string example: Workspace does not have an active paid plan required: - statusCode - error - message '404': description: The requested resource was not found content: application/json: schema: type: object properties: statusCode: type: number enum: - 404 example: 404 error: type: string enum: - Not Found example: Not Found message: type: string example: Resource not found required: - statusCode - error - message '429': description: >- You have exceeded the rate limit. Please check the rate limit docs for more information. content: application/json: schema: type: object properties: statusCode: type: number enum: - 429 example: 429 error: type: string enum: - Too Many Requests example: Too Many Requests message: type: string example: Rate limit exceeded required: - statusCode - error - message components: securitySchemes: ApiKeyAuth: type: http scheme: bearer ````