Act! Web API
JSON-based REST API for the Act! CRM database exposing contacts, companies, groups, opportunities, tasks, activity series, calendar, notes, history, documents, attachments, users, teams, preferences, analytics and tenant-defined custom entities — 410 operations across 31 resource areas. Collection reads accept OData v4 query options; requests can be batched at POST /api/$batch; webhooks are registered through the API itself. The database schema is discoverable at runtime through the MetadataInfo operations because Act! databases are user-extensible. Authentication is a JWT bearer token obtained from GET /authorize with HTTP Basic credentials and an Act-Database-Name header.
Act! Web API is one of 11 APIs that Act! CRM publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include CRM, REST API, OData, OpenAPI, and Webhook. The published artifact set on APIs.io includes API documentation, an API reference, an OpenAPI specification, and rate-limit docs.
This API exposes 29 operations across 29 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against 3 base URLs: https://apimta.act.com/act.web.api, https://{server}/{customer}-api/act.web.api, https://{server}/act.web.api.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Act! Web API declares
3 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
It accepts HTTP bearer tokens (JWT) (bearerAuth).
An API key is passed in the header as Act-Database-Name (actDatabaseName).
By default, every request must be authenticated.
basicAuth— HTTP Basic credentials (Act! user name and password, RFC 7617) presented to GET /authorize together with the Act-Database-Name header to mint a JWT bearer toke…bearerAuth— JWT bearer token returned by GET /authorize (RFC 6750). Sent as Authorization: Bearer on every API request.actDatabaseName— Name of the Act! database the request is scoped to.
Paths & Operations 29
Across 29 paths, the API surfaces 29 operations — 28 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 28
The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are act.web.api.Controllers.AnalyticsPipeline (14 properties), act.web.api.models.Analytics.MarketingLead (11 properties), act.web.api.models.Analytics.PipelineOpportunity (11 properties), act.web.api.models.Analytics.TaskListActivity (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Act! CRM 10
Other APIs Act! CRM publishes across the network.
This is an independent, third-party profile of Act! Web API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.