Build on SmartContact
Everything you can do in SmartContact, you can do through its public REST API: companies, contacts, deals, the timeline, tasks, meetings, campaigns, reports and more (120 operations). The app itself uses the same API, so nothing is held back.
Plugin marketplace: a developer portal (sign-up, sandbox workspaces, publishing and payouts) and an in-app plugin
marketplace are on their way. Until then, build private integrations for your own workspace with an API key, on any plan.
What's planned.
Quickstart
- In SmartContact, a workspace admin opens Settings › API keys and creates a key of type Integration, choosing the role it acts as.
The key looks like
sc_ab12cd34.…and is shown once. - Call the API with it as a bearer token:
curl https://app.smartcontact.online/v1/me \
-H "Authorization: Bearer $SMARTCONTACT_KEY" Create a company, then log a call on it:
curl -X POST https://app.smartcontact.online/v1/companies \
-H "Authorization: Bearer $SMARTCONTACT_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Harbourline Logistics", "website": "https://harbourline.example"}'
curl -X POST https://app.smartcontact.online/v1/activities \
-H "Authorization: Bearer $SMARTCONTACT_KEY" \
-H "Content-Type: application/json" \
-d '{"type": "call", "target_type": "company", "target_id": "<company id>", "outcome": "connected", "body": "Wants a demo"}' The company's timeline now shows the call, labelled with the key's name. Every change made through the API is also in the workspace audit log.
What you can build
- Integrations: sync companies and contacts with another system, push leads in from your website or tools, export to a warehouse.
- Marketing data: record campaigns, daily spend and touchpoints (ad clicks, email clicks, events) so Marketing ROI shows what paid off. Re-sending with the same
external_refnever duplicates. - Reports: run any saved or ad-hoc report through
/reports/runand use the results elsewhere. - AI agents: connect Claude, Gemini, Copilot or your own agent to the remote MCP server.
Next
- Authentication and conventions: keys, roles, errors, paging, dates and money.
- API reference: every operation, generated from the OpenAPI description, so it always matches the API.