> ## Documentation Index > Fetch the complete documentation index at: https://kiflo-b3d3c9c0.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Request partner influence > Ask your partner team to bring partner influence on one of your accounts, without naming a partner: a partner manager chooses one later, if and when they start a collaboration. The account the request targets is resolved from the candidate CRM records you send, in an order given by the source object type, and is the first of them whose account overlaps a partner account. An account can carry only one request waiting for an answer: a new request is refused while the latest one is still pending, and allowed once it has been accepted or refused. This endpoint requires a HubSpot-issued access token: the request is attributed to the user that token was issued for, which a Public API key does not identify. ## OpenAPI ````yaml /openapi.json post /v3/account-mapping/collaboration-requests openapi: 3.0.1 info: title: Kiflo Public API v3 description: "The Kiflo API allows you to have control over your integration and create the best experiences.\r\n\r\n***\r\n\r\n## Format\r\n\r\nThe API follows the REST standard using JSON to format requests and responses. \r\nDecimals are formatted using invariant culture, ie: using \".\" (dot) as a decimal sperator and no thousands separator. \r\nDates are formatted using ISO standards, in UTC format, including the timezone. Ex: 2015-03-25T12:00:00Z\r\n\r\n***\r\n\r\n## Security\r\n\r\nThe API is secured using an API token.\r\n\r\n**How to generate an API Access Token** \r\n 1. Open your [account settings page](https://app.kiflo.com/account/integration)\r\n 2. Go to the \"API Access Token\" section\r\n 3. Click \"Add\" button\r\n 4. Choose a name that will be used to identify the token and click \"Add\"\r\n 4. Copy the generate token\r\n \r\n> **Note:** For security reason, the generated API Access Token won't be visible after you close the settings page. Be sure to copy the generated token otherwise you won't be able to get it later.\r\n \r\n**How to authenticate on the API** \r\n \r\nTo authenticate on the API, send the generated token in the Authorization header using the Bearer scheme: \r\n`Authorization: Bearer #YOUR_GENERATED_TOKEN_HERE#`\r\n" version: v3 servers: [] security: [] paths: /v3/account-mapping/collaboration-requests: post: tags: - AccountMappingCollaborationRequests summary: Request partner influence description: "Ask your partner team to bring partner influence on one of your accounts, without naming a partner: a partner manager chooses one later, if and when they start a collaboration.\r\nThe account the request targets is resolved from the candidate CRM records you send, in an order given by the source object type, and is the first of them whose account overlaps a partner account.\r\nAn account can carry only one request waiting for an answer: a new request is refused while the latest one is still pending, and allowed once it has been accepted or refused.\r\nThis endpoint requires a HubSpot-issued access token: the request is attributed to the user that token was issued for, which a Public API key does not identify." requestBody: content: application/json-patch+json: schema: $ref: >- #/components/schemas/AccountMappingCollaborationRequestCreateRequestDto application/json: schema: $ref: >- #/components/schemas/AccountMappingCollaborationRequestCreateRequestDto text/json: schema: $ref: >- #/components/schemas/AccountMappingCollaborationRequestCreateRequestDto application/*+json: schema: $ref: >- #/components/schemas/AccountMappingCollaborationRequestCreateRequestDto responses: '200': description: >- Collaboration request created. The response has no body: the request is not readable through this API, so there is nothing to return. '400': description: >- Invalid request, no candidate record overlaps a partner account, or the resolved account already has a request waiting for an answer '403': description: >- The access token was not issued by HubSpot, the account mapping feature is not available, or the user cannot request partner influence security: - oauth2: - AccountMappingCollaborationRequest.Create - HubSpot components: schemas: AccountMappingCollaborationRequestCreateRequestDto: type: object properties: context: type: string description: >- What you need from your partner team. Plain text, required, up to 2000 characters. nullable: true sourceRecordId: type: string description: "The ID of the CRM record the request is raised from, in the CRM it comes from. Required.\r\nIt is the first candidate for the account the request targets, and is recorded on the request whether or not it is the one that resolves." nullable: true sourceObjectType: type: string description: >- The type of the CRM record Resels.Backend.Api.Public.Model.AccountMappingCollaborationRequests.v3.AccountMappingCollaborationRequestCreateRequestDto.SourceRecordId identifies: "companies", "contacts" or "deals". Required. nullable: true associatedCompanyExternalIds: type: array items: type: string description: "The IDs, in the CRM they come from, of the company records associated with Resels.Backend.Api.Public.Model.AccountMappingCollaborationRequests.v3.AccountMappingCollaborationRequestCreateRequestDto.SourceRecordId.\r\nConsidered after the source record itself. Optional." nullable: true associatedContactExternalIds: type: array items: type: string description: "The IDs, in the CRM they come from, of the contact records associated with Resels.Backend.Api.Public.Model.AccountMappingCollaborationRequests.v3.AccountMappingCollaborationRequestCreateRequestDto.SourceRecordId.\r\nConsidered after Resels.Backend.Api.Public.Model.AccountMappingCollaborationRequests.v3.AccountMappingCollaborationRequestCreateRequestDto.AssociatedCompanyExternalIds. Optional." nullable: true additionalProperties: false ````