How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nimble Tasks API

Task creation against contacts. 1 operation(s).

Nimble Tasks API is one of 12 APIs that Nimble publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Task and Productivity. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://app.nimble.com.

1 operations 1 paths 15 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://app.nimble.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Nimble Tasks API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Nimble-Token (ApiKey). By default, every request must be authenticated.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Tasks 1

Tasks management

POST
/api/v1/tasks
Create new task
post-task body → 201404409

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Accounts.User (21 properties), Tasks.Task (20 properties), Legacy.UserMetadata (11 properties), Contacts.ShortContact (8 properties). Each schema is shown below with its type and property counts.

Accounts.User
object
21 properties 20 required
Tasks.TaskRelatedObjectsSpec
object
Objects to associate with a task. Use related.contacts rather than the legacy relatedto field.
2 properties
Commons.Comment
object
5 properties 5 required
Tasks.TaskRelatedObjects
object
4 properties 4 required
Contacts.ShortContact
object
8 properties 7 required
Errors.ValidationError
object
request was malformed
5 properties 3 required
Tasks.Task
object
20 properties 20 required
Legacy.UserMetadata
object
11 properties 11 required
Accounts.ShortUserInfo
object
5 properties 5 required
Deals.ShortSavedDeal
object
5 properties
Contacts.ContactType
string
Tasks.NewTaskSpecification
object
8 properties 1 required
Sequences.SequenceBriefInfo
object
2 properties 2 required
Errors.NotFoundError
object
2 properties 2 required
Settings.UserPermissions
object
users permission

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nimble-tasks-api-openapi.yml Raw ↑

Other APIs Nimble publishes across the network.

Nimble Activities API
Nimble Contacts API
Nimble Contacts Fields API
Nimble Contacts Pipelines API
Nimble Deals API
Nimble Deals Fields API
Nimble Deals Pipelines API
Nimble Deals Pipelines Fields API
Nimble Leads API
Nimble Messages API
Nimble Users API
Where this information came from

This is an independent, third-party profile of Nimble Tasks 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.