The API Report CardAPI Index
Nimble

Nimble API

Social CRM / SMB Relationship Management · nimble.com

Nimble publishes a self-serve v1 REST API at app.nimble.com/api/v1 covering contacts, deals, custom fields, pipelines, and search. Per-account API keys come straight from settings; OAuth 2.0 apps require emailing api-support for registration. No native webhooks, so integrations poll.

Last verified: July 2026Marketing & Sales
API GRADE
B
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented v1 REST API at app.nimble.com/api/v1 with resources for contacts, deals, fields, and search.
AccessGOODPer-account API keys are self-serve from settings; OAuth app registration goes through an email to api-support.
CoverageGOODContacts and deals CRUD with bulk operations, custom field management, pipelines, search, and message drafts.
AuthGOODOAuth 2.0 with basic, contacts, and deals scopes plus refresh tokens; bearer API keys work as an alternative.
Docs & DXGOODDocs include Python and Ruby examples and a community Ruby gem; no first-party Node, .NET, or Java clients.
StabilityGOOD
Supergood: Nimble shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Nimble scores B on the API Report Card. Nimble publishes a self-serve v1 REST API at app.nimble.com/api/v1 covering contacts, deals, custom fields, pipelines, and search. Per-account API keys come straight from settings; OAuth 2.0 apps require emailing api-support for registration. No native webhooks, so integrations poll.

Tried to integrate with Nimble?
SOURCES
No documented native outbound webhooks, integrations must poll contacts/deals/teams endpoints or rely on Zapier / Make triggers for change detection apitracker.io
Per-account rate limits are enforced but undocumented; HTTP 429 is returned without published request-per-minute/day ceilings, forcing trial-and-error backoff apitracker.io
OAuth application registration is gated behind an email to api-support@nimble.com (manual review) rather than a self-serve developer console support.nimble.com
Official SDK coverage is limited, only Python and Ruby examples in the docs and a community Ruby gem; no first-party Node, .NET, Go, or Java client nimble.com
Search API uses a custom query syntax with synthetic fields that is sparsely documented and inconsistent across resources nimble.com
Pagination is exposed only via a meta key on list responses and is not consistent across all endpoints stitchflow.com
No published bulk-export endpoint for full account data, large extractions require paginating every object/engagement type apitracker.io
Engagement / message history is the most-cited 'lost data' category during migration off Nimble, indicating the export surface lags the import surface softwarefinder.com
2 GB per-user storage cap fills quickly because Nimble syncs full Gmail/Outlook history, forcing constant cleanup or paid storage add-ons g2.com
Email-sequence and group-message sending limits are restrictive for any real outbound motion; users report duplicate emails and lack of inbox subfolder access g2.com
Mobile app is unreliable and feature-thin relative to desktop, limiting field-sales utility softwarefinder.com
Reporting and analytics depth is limited vs HubSpot/Salesforce, no true custom dashboards or BI-grade pivots getapp.com
Marketing automation is basic, no advanced branching, scoring, or attribution beyond simple sequences and group sends copy.ai
Recurring bugs and system instability cited across G2/Capterra reviews; support is responsive but issues recur g2.com
Mapping and intuitive search features feel dated compared to modern CRMs like Attio or Folk g2.com
Integration breadth lags larger CRMs, many connectors are Zapier-mediated rather than native getapp.com
Data export and migration off Nimble frequently loses activity history (notes, message threads, attachments) softwarefinder.com