Parameters
All available parameters for the generate-content endpoint.
Autobound’s API returns the most relevant insights based on BOTH context on the user (seller) and contact (prospect). Flexible parameters lets you generate insights for a specific seller on your team, or a user at another company.
Insights may include social activity, news, financial trends, hiring signals, and more—at both the contact and company level. (full list here)
Parameter Overview
Parameter | Description | Type | Required |
---|---|---|---|
contactEmail | Email address of the contact | identifier | One of these 3 |
contactLinkedinUrl | LinkedIn URL of the contact | identifier | One of these 3 |
contactCompanyUrl | Domain of the contact’s company | identifier | One of these 3 |
userEmail | (Optional) email of user you want to use for determining insight relevance. Falls back to user's email address that created API key, if not passed in. | identifier | Optional |
userLinkedinUrl | (Optional) LinkedIn URL of user. Falls back to user who created API key if not passed in. | identifier | Optional |
userCompanyUrl | (Optional) Domain of the user’s company. Falls back to user who created API key if not passed in. | identifier | Optional |
insightSubtype | (Optional) Specify one or more insight subtypes to prioritize | string or array | Optional |
Required Prospect Identifiers
To generate insights, you must provide at least one of:
contactEmail
: e.g."[email protected]"
contactLinkedinUrl
: e.g."linkedin.com/in/prospect"
contactCompanyUrl
: e.g."company.com"
If the system cannot resolve the contact but can resolve the company, it will return company-level insights only.
Optional User Context (Improves Relevance)
Passing in user-level fields (such as userEmail
, userCompanyUrl
, or userLinkedinUrl
) enables Autobound to:
- Personalize the insight ranking based on your product, ICP, or industry
- Highlight signals more aligned with your perspective or domain
- Leverage shared experience between user and prospect when available
This feature is powered by an algorithm that ingests data on ~100 contextual signals across both parties.
About insightSubtype
insightSubtype
Use insightSubtype
to return only specific types of insights.
Supported formats:
- A single string:
"linkedinPost"
- An array of strings:
["linkedinPost", "companyFunding", "hiringVelocity"]
Behavior:
- The system attempts to resolve each subtype
- Each returned insight is still ranked by contextual relevance
- Up to 2 insights per subtype will be returned (max 10 subtypes per request)
📚 View the full list of supported insight subtypes
Let me know if you want a diagram showing how resolution and ranking works under the hood.
Updated 4 days ago