accountpaceManage API keys →
DEVELOPERS / INTEGRATION PARTNERS

AccountPace API

Version 1 · Pilot · Updated November 13, 2026

Turn company context into an account priority assessment, three coordinated buying paths and personal outreach drafts—directly from a Clay table or another server-side workflow.

HTTP API pilot
Integration status

AccountPace provides a bearer-authenticated HTTP endpoint compatible with Clay’s HTTP API action. This is a pilot implementation, not a native Clay marketplace integration or a claim of Clay partner approval. A customer’s Clay connection requires its own setup and end-to-end verification.

Authentication & access

Approved AccountPace workspace users can create a key in Clay & API connections. Partner and beta users must complete the applicable agreement and administrator approval first. Keys are tied to the issuing user’s private workspace; one user’s key cannot select or access another user’s workspace.

Authorization: Bearer YOUR_ACCOUNTPACE_API_KEY
Content-Type: application/json

Scope: accounts:evaluate. Keys are shown once, stored as hashes, expire after 90 days and can be revoked immediately. Up to five active keys per user are allowed. The server rechecks workspace access on every request. Treat a key as access to the matching account strategy in that workspace. Do not put keys in URLs, browser code or Clay table cells.

No ChatGPT browser session is required for the external endpoint. API keys do not grant access to HubSpot tokens, contact exports, workspace editing or email delivery. Browser-based key management uses the existing AccountPace sign-in.

Evaluate an account

POST https://accountpace.com/api/v1/accounts/evaluate

One request evaluates one company. The response combines caller-supplied context with an unambiguous matching account in the key owner’s workspace. This operation does not save or modify accounts. It does not crawl the internet or independently verify source contents.

FieldTypePurpose
domainstring · requiredCompany domain, such as example.com. HTTPS website URLs are normalized to the domain.
company_namestring · optionalUp to 200 characters. Falls back to the saved account name or domain.
business_casestring · optionalUp to 5,000 characters describing the specific growth or operating question. Falls back to the saved use case or objective.
commercial_productboolean · optionalWhether the caller has established a commercially available product.
paying_customersboolean · optionalWhether the caller has established paying customers.
b2bboolean · optionalWhether the company sells to other businesses.
signalsarray · optionalAt most 20 growth or operating signals, as described below.

Each signal requires type and description (up to 1,000 characters). Optional fields: source_url (HTTP/HTTPS, up to 2,000 characters) and observed_at (valid YYYY-MM-DD, no future dates). Omit unknown booleans and dates rather than inventing values. Unknown fields are rejected.

Signal types: funding, acquisition, new_revenue_leader, expansion, sales_hiring, investor_ownership, customer_growth.

Example request · fictional company

curl --request POST \
  'https://accountpace.com/api/v1/accounts/evaluate' \
  --header 'Authorization: Bearer YOUR_ACCOUNTPACE_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "domain": "bentwood.example",
    "company_name": "Bentwood (fictional)",
    "business_case": "Expand an established AI product into adjacent enterprise use cases.",
    "commercial_product": true,
    "paying_customers": true,
    "b2b": true,
    "signals": []
  }'

How the pilot ranking works

This is transparent rules-based decision support, not a prediction of purchase. When all three ICP booleans are supplied: any false criterion gives priority 1; all true gives priority 3; adding a business case and one distinct dated, sourced growth driver within 36 months gives priority 4; two or more gives priority 5. Investor ownership alone does not raise the score. Source URLs and dates are caller assertions, not verified evidence.

If the three criteria are incomplete, the API uses a matching saved ICP ranking when available; otherwise priority_score is null and the response explains the missing information. This pilot ruleset does not emit priority 2 except when that is the customer’s saved ranking.

Response fields

Successful requests return HTTP 200 with a data object and a request_id. Important fields to map into Clay:

FieldMeaning
data.priority_scoreInteger 1–5, or null when insufficient information is available.
data.priority_basiscaller_supplied_rules, saved_workspace_assessment, or insufficient_information.
data.priority_reasons / missing_fieldsWhy the assessment was made and which ICP inputs are missing.
data.business_case / business_driversAccount context and supplied signals, each labeled as not independently verified.
data.buying_groupsBudget owner, technical buyer and executive stakeholder: suggested titles, pain to validate, channel and cadence.
data.next_actionRecommended next step, respecting saved account outreach controls.
data.outreach_draftsRole-specific subject and body drafts with review_required=true. Names and signatures remain placeholders.
data.outreach_controlsSaved do-not-contact, pause and technical-concern flags.
data.workspace_match / limitationsWhether a unique saved account matched, plus interpretation limits.
data.assessment_versionRuleset identifier: pilot-rules-1.

Suppressed or paused accounts receive no outreach drafts. Accounts without a business case receive no drafts. A technical concern changes the next action to resolving the concern. Importing or evaluating data never marks buyers as engaged or advances deal readiness. Multiple saved domain matches do not supply a ranking or business case; restrictive outreach flags from any match still apply.

Abbreviated response · fictional example

{
  "data": {
    "api_version": "1",
    "assessment_version": "pilot-rules-1",
    "domain": "bentwood.example",
    "company_name": "Bentwood (fictional)",
    "workspace_match": false,
    "priority_score": 3,
    "priority_basis": "caller_supplied_rules",
    "missing_fields": [],
    "business_drivers": []
  },
  "request_id": "unique-request-identifier"
}

The full response also includes the fields described above. See the OpenAPI specification for the complete contract.

Connect from Clay

  1. Create an AccountPace key in Clay & API connections.
  2. In Clay, add an HTTP API enrichment to your company table.
  3. Create an HTTP API (Headers) account and save Authorization with value Bearer YOUR_ACCOUNTPACE_API_KEY. Use Clay’s saved credential account rather than a visible column header value.
  4. Set the method to POST, URL to https://accountpace.com/api/v1/accounts/evaluate, and Content-Type to application/json.
  5. Use Clay’s column selector to map the domain, business case and known qualification fields into the request. Boolean values must be JSON booleans, not strings.
  6. Test one row, inspect data.priority_basis, then map the response fields into columns. Respect the rate limits before running more rows.

Example body to adapt using Clay’s column picker:

{
  "domain": "/Company Domain",
  "company_name": "/Company Name",
  "business_case": "/Business Case"
}

The slash labels above are illustrative Clay column references, not literal company data. Omitted qualification fields may result in an insufficient-information assessment. No Clay API key is needed by AccountPace for this inbound flow. Clay sends requests to AccountPace using the AccountPace key.

Clay’s official HTTP API setup guide ↗

Limits, errors & retries

Pilot allowance: 30 authenticated requests per minute and 1,000 per UTC day per key. Validation failures after authentication count toward the allowance. Maximum request body: 64 KiB. Requests are synchronous, one account at a time. No batch endpoint, webhook subscription or uptime SLA is offered in this pilot.

StatusMeaning
400Invalid JSON, domain, field, signal or date. Correct the input.
401Missing, invalid, expired or revoked API key.
403Scope or workspace approval is missing or no longer active.
404 / 405Unknown endpoint / unsupported method.
413 / 415Request too large / JSON content type required.
429Allowance reached. Honor the Retry-After response header.
503Temporary failure. Retry with exponential backoff.
{
  "error": {
    "code": "unauthorized",
    "message": "API key is invalid, expired or revoked."
  },
  "request_id": "unique-request-identifier"
}

Include the request ID in support requests; never include your API key. Repeating an evaluation does not create records, but each request consumes allowance. Server-side HTTP use is supported; browser cross-origin access is not enabled.

Data handling & partner review

The evaluation endpoint does not persist request bodies or generated drafts. It reads matching strategy in the issuing user’s workspace and returns the evaluation to the requesting integration. Key metadata, counters and last-use timestamps are stored for access control and usage limits. Your provider may retain responses under its own settings. See our Privacy Policy, Terms of Service and Partner Program Terms.

For integration review, a test workspace and scoped key can be provisioned after access approval. Contact info@accountpace.com. No shared production key is published in this documentation.