> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/developers/api-reference/account-mapping-collaboration-requests/request-partner-influence.md). # 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. ```json {"openapi":"3.0.1","info":{"title":"Kiflo Public API v3","version":"v3"},"security":[{"oauth2":["AccountMappingCollaborationRequest.Create","HubSpot"]}],"components":{"securitySchemes":{},"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}}},"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"}}}}}} ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs-vnext.kiflo.com/developers/api-reference/account-mapping-collaboration-requests/request-partner-influence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.