Advice and answers from the Nimble Team

To use API keys to access your account programmatically please follow the guide at https://nimble.readthedocs.io with two important changes:

  1. Send API request to https://app.nimble.com instead of https://api.nimble.com
  2. The only form of accepted authentication is through HTTP header. Your API request must have Authorization header with value like this: Bearer API-KEY.

Python request example

import requests 

apikey = "YOUR_API_KEY"

result = requests.get("https://app.nimble.com/api/v1/myself", headers={"Authorization": "Bearer " + apikey})

print(result.json())

cURL example

curl -H "Authorization: Bearer YOUR_API_KEY" https://app.nimble.com/api/v1/myself

 

API Access Info


The Nimble platform offers access to the stored data via our APIs. Currently, mainly contact data is accessible via our REST API. We are constantly improving our API and releasing additional functionality in the following order:
 
 
GET/CREATE/UPDATE/DELETE notes related to contacts - available
CREATE related activities - available
GET related activities - 2013
GET related messages - TBD
GET related social - TBD
MERGE contact - TBD
 
Given the early state of the API, some aspects of the API are subject to change.
 
We are building the API with a few main use cases in mind: widgets/extensions to Nimble, web clients (including our own), mobile clients. and ultimately 2-way data integrations with other services. We aspire to make an API that is simple to use, easy to read, and flexible.
 
For Nimble API Access, please email  api-support@nimble.com and include the following:
 
App Name
App Description
Redirect URL for oAuth callback
 

To read our API documentation,
please visit http://nimble.readthedocs.io/en/latest/
 
 

Important note to developers:

If you have started to receive a "redirect_uri_mismatch" error when making the token request, please check to make sure that if you provide a callback uri as part of the original authorization request that you are also including it in the token request. The oauth spec states that if the redirect uri is part of the authorization request then it must also be included and match exactly in the token request. We have found that our upgraded oauth service enforces this whereas our previous one did not.

http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-4.1.3

If you have any questions, please send us an email at api@nimble.com

Did this answer your question?