Authenticated requests
API and MCP enrichment operations require an authorized bearer credential.
Explore Authenticated requestsTargetWise trust centre
Security and data handling for your integration.
Explore how TargetWise authenticates API requests, protects provider credentials and validates enrichment operations. Find the information and contacts your team needs for its security and privacy review.
Integration securityControlled access
Workspace credentials and request validation protect access to TargetWise enrichment operations.
Authenticated API and MCP access
Server-side provider credentials
Validated enrichment requests
Security controls
How TargetWise handles your requests.
Authentication, credential isolation and input validation are built into the API gateway.
Server-side provider credentials
The upstream data credential is read from server configuration and is not forwarded from, or returned to, the caller.
Product-specific contracts
Inputs are checked against the supported identifiers and fields before an upstream request is made.
Eleven metered data tools
Eleven MCP tools expose prospecting, enrichment and lookup—not CRM writes or outreach actions.
Explore Eleven metered data toolsExplicit missing data
Responses distinguish matched, partial and not-found results and list unresolved fields instead of fabricating values.
Customer-owned action
TargetWise returns enrichment data; the customer controls acceptance, merging and downstream decisions.
Security review
Give your review team the context it needs.
Describe the product operation, identifiers submitted, fields requested, delivery path and destination of the response.
Contact TargetWise with your questionnaire and document requirements so the team can address your integration.
- REST API or MCP
- Input and output fields
- Account and credential model
- Downstream storage and action
- Required review documents
Traceable integration
Follow a request from input to result.
Send a LinkedIn profile URL, or a name and company identifier. Select email, phone or both. The response includes a request ID, retrieval timestamp, result status and any unresolved fields.
Keep the request ID alongside the CRM update. A partial result can fill an empty email field while leaving a missing phone unchanged.
- Documented input schema
- Selectable contact fields
- Matched, partial and not-found outcomes
- Request reference for troubleshooting
Frequently asked questions
Clear answers before you continue.
Where to find security information, legal documents and help with your review.
Need a review?
Talk to us about your security requirements.
Share your intended integration and the information your review team needs.